Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Forum Replies Created

Viewing 15 posts - 331 through 345 (of 7,398 total)
  • Author
    Posts
  • in reply to: #34408
    peterlaursen
    Participant

    hmmm .. it looks like some additional 'security feature' affects this particular OS/Windows version.

    Also on the GUI wizard you can specify the log and session file.

    in reply to: #34673
    peterlaursen
    Participant

    Well. then it would also apply to “double quotes” and maybe even more (`backquotes` ?).

    I am not sure if we are able to consider what is 'to the right of' current cursor position. But you could say that we could double the quote if the same kind of quote if the same kind of quote is prsent to the left of current cursor position with no whitespace in between.

    But I would hate to replace/overwrite the standard copy/paste behavior for all users. It should be an additional option then I think. I also know how much effort it would take to implement such in Scintilla (our editor is based on the Scintilla library).

    We will think about it and discuss. How often do you have a quote inside a quoted string in your statements?

    in reply to: #34668
    peterlaursen
    Participant

    @Lars .. what is the MySQL server version?

    As I understand discussion in bugs.mysql.com , 'user management with wildcards' does not work with recent servers anyway. Your PLESK probably also does not use CREATE USER/GRANT syntax, but INSERTs directly to privileges tables (what is not recomended).

    We had 2 different hostings over the last 6–7 years both using PLESK and we never faced this problem ourselves, so I wonder if your server is running a setup of very old software.

    in reply to: #34662
    peterlaursen
    Participant

    I have alredy relied here http://forums.webyog.com/index.php?showtopic=7332

    SQLyog connects to MySQL servers (but not to Microsoft SQL Servers) on both local and remote servers.

    If you want to use Microsoft SQL Server you cannot use SQLyog as the client. If you want to use SQLyog as a database client the server must be a MySQL server.

    in reply to: #34661
    peterlaursen
    Participant

    There is no such thing as “MYSQL SERVER 2005” (but there is a “Microsoft SQL SERVER 2005”). You are confusing (Microsoft) SQL Server and MySQL (currently owned by Oracle). “SQL Express” is is free edition of (Microsoft) SQL Server. This is the homepage of MySQL: http://www.mysql.com/ (and it is completely unrelated to Microsoft)

    SQLyog is a client for MySQL and no other database server – also not (Microsoft) SQL Server. Please refer: http://faq.webyog.com/content/32/65/en/what-kind-of-databases-does-sqlyog-support.html . If you want to use (Microsoft) SQL Server you cannot use SQLyog as the client.

    in reply to: #34660
    peterlaursen
    Participant

    Please elaborate “At Table Edit window, AND (my emphasis) at Indexes and Foreing Keys tabs”

    What is 'table Edit WIndow'? The COLUMNS-tab of ALTER TABLE dialog? Columns are listed in the order as returned by SHOW CREATE TABLE. I cannot think of any tool that does not. There is an option to 'reorder columns'.

    We don't use “objects modification date”. It is plain impossible. The MySQL server does not expose such historical information at all.

    So would you mind elaborate?

    in reply to: #34659
    peterlaursen
    Participant

    I do not see how this question is related to SQLyog? SQLyog is one client and your script is another. And they work independent of each others.

    But is the “PY”, you are referring to this http://stackoverflow.com/questions/372885/how-do-i-connect-to-a-mysql-database-in-python ?

    in reply to: #34656
    peterlaursen
    Participant

    Why can't you access the HISTORY tab? Doesn't it display? Does nothing happen when you click on it?

    Please elaborate. Also please tell your SQLyog version.

    in reply to: #34651
    peterlaursen
    Participant

    There was no attachment(s) – but an awful lot of whitespace – in your post!

    Could you try to attach again? Or alternatively mail to [email protected].

    in reply to: #34633
    peterlaursen
    Participant

    SQLyog is not “switching to latin2 for itself and the connection”.

    Undoubtedly the reason is that you have the option “–character-set-client-handshake” set to FALSE in server configuration.

    Please refer http://dev.mysql.com…lient-handshake about this. (and I should have listed this as a possible reason in the first place too, but I forgot. It simply looked too much like a font problem)

    It is not possible for a client to check for this. The option is not exposed as a variable. User will have to know. I posted a bug report about same to MySQL: http://bugs.mysql.com/bug.php?id=69997

    in reply to: #34631
    peterlaursen
    Participant

    + Also please tell your SQLyog version. Anyway from version 6.0 and upwards there should be no difference in this respect.

    in reply to: #34626
    peterlaursen
    Participant

    If you are considering upgrading, please contact [email protected]. You will of course not need to pay the full price for Enterprise or Ultimate as you already paid for Professional.

    in reply to: #34630
    peterlaursen
    Participant

    This does not look like a double encoding problem. The 'SQUARE' (or sometimes Question Mark in some programs) indicates to me that the particular character is not mapped to a glyph in the font used.

    Could you please try to select another font for display? You do so in tools .. preferences .. 'Font&Editor settings' tab.

    There may be a problem with the polish “ł” character and the font used currently. What is the OS? And what is the font currently used?

    in reply to: #34635
    peterlaursen
    Participant

    No, currently 'Custom Objects' can only be defined based on a SQL query. And thus adding OS-related objects is not possible.

    in reply to: #34627
    peterlaursen
    Participant

    Issue confirmed. But I consider this somewhat different an issue than what I understand you do.

    The logfile specification is intended to be a commandline parameter. It is not saved in the (XML-)jobfile. The same job specification/jobfile can be started with different commandline parameters.

    I don't know if you know this FAQ: http://faq.webyog.co…gent_-sja.html:

    ” You can start SJA from SQLyog ‘Powertools’ menu or from command line. Command line syntax is

    sja “jobfile.xml” –l”log.txt” –s”session.xml”

    The -s and -l parameters for specifying the session file and the log file are optional. A complete file path can be specified (using the quotes is necessary if there are spaces or a ‘:’ in the path). That is useful if you don’t have write privilege to the installation folder. If not specified default values logfile.txt and session.xml are used and file are placed in the directory from where SJA runs.”

    (..and honestly, I am not sure if the last sentence here is still correct. I think that when no jobfile and sessionfile is specified both files should go to user's 'user profile' on Windows. And it may be the case and if so the FAQ was not updated properly). We will check this)

    The default setting for the log file in the wizard is {system_drive}:Users{user}AppDataRoamingSQLyogsja.log – ie. user's 'user profile'. The wizard has no setting for the session file. The session file is temporary, but will need to be specified to a folder where user has write-access, just like is the case for the log file. So this is an inconsistency. It also never was the purpose to specify different logfiles for different jobs exectued interactively. The purpose was to ensure an option for user to specify a folder where he has write access (and was – as far as I remember – originally implemented on request by Linux SJA users)

    So I think the option to specify the log file in the Windows wizard should simply be removed. Logfile and Sessionfile belong in user's 'user profile' on Windows for jobs started interactively (ie. from the wizard). I think the current implementation is a relic from before version 8.16 (where we started placing all not read-only files in user's 'user profile'). It is also inconsistent that there is a setting for the logfile and not for the sessionfile in the wizard.

    The -l and -s parameters should still work/will still work as commandline parameters, of course.

    We will discuss this. We have a few additional holidays around this weekend so expect a conclusion only by end of next week. You are welcome to comment in between.

Viewing 15 posts - 331 through 345 (of 7,398 total)