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

Forum Replies Created

Viewing 15 posts - 121 through 135 (of 7,398 total)
  • Author
    Posts
  • in reply to: Sql Database #35302
    peterlaursen
    Participant

    Please refer this https://dev.mysql.com/doc/refman/5.6/en/ansi-diff-select-into-table.html

    MySQL Server doesn’t support the SELECT … INTO TABLE Sybase SQL extension. Instead, MySQL Server supports the INSERT INTO … SELECT standard SQL syntax, which is basically the same thing. See Section 13.2.5.1, “INSERT … SELECT Syntax”“.  

     

    So your statement is not supported by MySQL. However he error message is not good and not helpful to identify the problem.  But it is an error message generated by the MySQL server and not by SQLyog. Error message quality problems are frequenly reported to bugs.mysql.com. You may decide to report this one as well.

     

    Note that also the [square brackets] are not MySQL syntax. It is Microsoft (SQL Server and Access) syntax.  MySQL uses `backticks` for quoting identifers (unless ANSI sql_mode is used. In that case it is “double quotes”).  The complete MySQL statement syntax is documented here:  https://dev.mysql.com/doc/refman/5.6/en/sql-syntax.html

    in reply to: "info" Tab Deadly When Clicking On Expand Database #35320
    peterlaursen
    Participant

    causes it to run a huge query to show database info”.  Yes, of course.  It will query the server in order to get informaton to populate the tab with information fro the currently selected object. This is the purpose of the INFO tab.

    in reply to: Networking Issue With Large Queries #35326
    peterlaursen
    Participant

    It is not unusual with (cheap) shared hosting that they will kill queries runnng for longer than a specific time. This is in order to protect other users on the same server against a de facto ‘denial of service’ caused by poorly written queries by one user (examples of this: 1) call to a routine entering an infinite loop 2) full cartesian joins (explicit or implict) of huge tables as it may happen for instance when using a subquery on MySQL versions that have poor subquery optimization (what all servers older than MySQ 5.6 have).).

    in reply to: Sql Database #35300
    peterlaursen
    Participant

    Please tell your SQLyog version.

     

    I also do not understand “Perhaps, this happens due to different database name”. Please elaborate in detail how to trigger this. 

    in reply to: Sqlyog 12.1 Flat Design #35292
    peterlaursen
    Participant

    Please read my concluding comment here: http://blog.webyog.com/2015/03/26/introducing-sqlyog-12-1-fresh-modern-design/ 

     

    We did not expect this change to go uncommented by users and also not that we would not have to make adjustments after the 12.1 release. However we have to realize that Windows 10 is the “future Windows” for as much time as we can look forward – and that is so, no matter if you and I like it or not. Windows XP is dead , the remaining service life of WinVista is 2 years and for Win7 it is 5 years. We need to aim our business towards the future.”  

     

    Windows is changing rapidly. And it never was defining the path of oru developments when a user threatened to stop using the program.  This has happened several dozens of times already.  We are doing better  paying attention to the majority of users (and I bet they will be Windows 10 users soon).  Also we cannot afford nostalgia.  IAlso i really does not matter if you and  like Win 8/10 or not.  From this summer Windows 10 will be THE Windows. 

     

    Next release will have the fix for icons display  display for users using XP/Vista/Win7/ ‘classic’ theme (an option WIn8/8.1/10 do not have).  Also some icons and other will be reworked being less ‘pastel’ (probably – our designer has just started today – but I asked for this myself) . We will take the discussion from there after next release. I do not exclude more changes including user options later, but nothing has been decided about it yet. 

    in reply to: Load Data Local Infile Forbidden #35315
    peterlaursen
    Participant

    This looks OK to me.  But I also understand that the problem has gone away now. I am not sure what the reason could have been.

    in reply to: Importing Csv File Adding 0 #35317
    peterlaursen
    Participant

    As far as I can understand this is an issue with MySQL (and the way you use it) and not with SQLyog.  You are using LOAD Data and this statement is executed on the server. It would be the same if you executedteh same LOAD DATA statement with any client.

     

    How is the column you import to defined? Execute “SHOW CREATE TABLE tablename;” and se.  iIt should not by chance be something like an INT(5) using ZEROFILL option? 

    (refer MyQL documentaton https://dev.mysql.com/doc/refman/5.5/en/numeric-type-attributes.html: ” When used in conjunction with the optional (nonstandard) attribute ZEROFILL, the default padding of spaces is replaced with zeros. For example, for a column declared as INT(4) ZEROFILL, a value of 5 is retrieved as 0005.”

    in reply to: Copy Sqlyog Connection Definitions To Other Computer #32733
    peterlaursen
    Participant

    There also is an option in menu .. tools .. Export/Import Connection details.

     

    (maybe there wasn’t when this thread started) 

    in reply to: Load Data Local Infile Forbidden #35313
    peterlaursen
    Participant

    I meant “SHOW GRANTS;”

     

    But anyway. let us see if it happens again. 

    in reply to: Load Data Local Infile Forbidden #35310
    peterlaursen
    Participant

    I have been googling the error “Load data local infile forbidden”. I can only find it in a PHP-context. The error received if ‘local_infile’ variable is the culprit is “ERROR 1148: The used command is not allowed with this MySQL version” (refer: https://dev.mysql.com/doc/refman/5.5/en/load-data-local.html).

     

    I believe this is a configuration issue of some kind on the server. If you try any other client, such as ‘mysql’ commandline and executing same statement you will undoubtedly receive the same error. You can try.

    in reply to: Load Data Local Infile Forbidden #35309
    peterlaursen
    Participant

    When you are getting the error “Load data local infile forbidden” was there an error no. too? Please provide a screenshot of the error dialog. This would help us to determine the context/the origins of the error message.

     

    Also please connect with SQLyog and execute “SWO GRANTS;” and paste the result here. 

    in reply to: Sqlyog Support Of Webdrive (mapped Drives) #35283
    peterlaursen
    Participant

    I tried with Webdrive /TRIAL) mapping my Dropbox store to a local drive letter.  It works fine. 

     

    if you don’t see the drive letter in SQLyog, then please check if you see it in Wndows eExplorer/My Computer.

    in reply to: Sqlyog Support Of Webdrive (mapped Drives) #35282
    peterlaursen
    Participant

    All of my tables and queries are stored on the shared drive mapped .. ”  i don’t understand how TABLES can be stored there. Tables are stored by the MySQL server . And SQLyog newer reads table files. It simply queries the MySQL server. 

     

    if a mapped drive is available for the OS/Wndows, it also is available for SQLyog. There is no change in SQLylog 12.1 causing any changed behavior here. I also verified for myself that I can use a mapped drive with SQLyog 12.1  (shared from another Windows machine on the network (not webdrive.com, but it simply does not matter: if Windows exposes a shared drive to SQLyog with a drive letter, SQLyog sees it as a local drive).

     

    Are you sure that there was not an outage of misconfiguration? 

    peterlaursen
    Participant

    SQLyog displays the MySQL user used for connection to MySQL.

    in reply to: Data Synchronization Wizard Fails #35269
    peterlaursen
    Participant

    As this is reproducible one server and not another – and with same data –  it must have something to do with a specific server environment/configuration. To find out what it exactly is causing tis without access to the server, would for us be like searching a needle in a haystack with our eyes blindfolded.

     

    Was it possble that we could have temporary read access to the data on this server (on another ‘faked’ dataset where it is reproducible)? If so please send credentials and details to [email protected]. If your client will not allow us to access the real data, then please try

     

    1) duplicate the problematic table (dump this table, and import to another database, or just to a new differently named table, for instance) 

    2) verify if problem persists with the new duplicated table s well. 

    3) (if required) delete most ofte data in this table (say except for 50 or 100 rows), ‘fake’ sensitive data in remaining rows, again verify that problem persists.

    4) provide us access to the duplicated table.  

Viewing 15 posts - 121 through 135 (of 7,398 total)