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

Forum Replies Created

Viewing 15 posts - 3,076 through 3,090 (of 7,398 total)
  • Author
    Posts
  • in reply to: #26213
    peterlaursen
    Participant

    I see your point .. you create a SP, next change it somehow . If the DROP statment was there you could keep the same window open.

    I am not aware that this was changed and not why either. What was the version you used before?

    in reply to: #26218
    peterlaursen
    Participant

    We all are pretty much tired of the server error message 1064 “You have an erro in your SQL syntax. Please refer to the documentation …” The most simple BASIC interpreter displays better error messages!

    But we have no immediate plans to implement such parsing functionalities in SQLyog. We basically think this is a server functionality.

    In the SQLyog ENTERPRISE version there is autocomplete and in every version you can doubleclick an object in the Object Browser and it will be copied to the active editor tab.

    in reply to: #26207
    peterlaursen
    Participant

    EXPLAIN is a server functionality. EXPLAIN EXTENDED is supported with recent server versions.

    EXPLAIN (EXTENDED) … can be executed for every SELECT statement (and only SELECT statements)

    In MONyog go to 'processlist' page to find the EXPLAIN option.

    in reply to: #26211
    peterlaursen
    Participant

    It is the MYSQL SERVER that converts to lowercase. This is default for MySQL on Windows! This would happen like that with any client!

    To avoid that insert in the [mysqld] section of the MySQL configuration file (my.ini) this line:

    lower_case_table_names = 2

    and restart the server.

    MySQL docs at:

    http://dev.mysql.com/doc/refman/5.0/en/ide…ensitivity.html

    .. and btw: this has been asked and replied to a couple of times before here.

    in reply to: Ms Access Not Importing #24189
    peterlaursen
    Participant

    Looks like this one EXPORTs to MySQL with the MyODBC driver (not imports with the access driver).

    in reply to: Ms Access Not Importing #24188
    peterlaursen
    Participant
    maxhugen wrote on Mar 24 2008, 11:12 PM:
    During the migration, the status window shows each table schema being successfully imported, but at the end the msg '[Microsoft][ODBC Microsoft Access Driver] Query support unavailable.' is repeated.

    The error is mentioned here but with not much additional info:

    http://support.microsoft.com/kb/172570

    (more here

    http://search.microsoft.com/results.aspx?q…&OtherSite=

    .. but almost the same!)

    I wonder if you are trying to import some 'saved queries' (not tables)? If so try to omit. Also you can try to 'narrow' it to a specific table.

    Can you share a .mdb file where this is reproducable? I still think it might be related to some settings with the file itself.

    If you can share such file please keep as small as possible and please zip and zip with the jobfile! Create a ticket if you want privacy.

    I think we should check some of this:

    Is it a common problem or a problem with a single file?

    Did you check security settings/properties for the file?

    What Access version was used for creating this file/the files?

    On what Windows version are you doing this? Driver version?

    Can you view data in Access itself?

    Do you have an option to copy the file to another computer?

    Was the database created as the same user and on the same as you are when trying to import.

    (my apology if you replied some of it already).

    etc. etc. …

    If you can do it is fine, but you can also let us.

    Finally try if you can import into another program with ODBC (another Access database for instance)? If yes will this new one import?

    in reply to: #26204
    peterlaursen
    Participant

    You have posted in the MONyog category, but as you are referring to “Enterprise evaluation” it must have been SQLyog you downloaded. SQLyog has no GUI query analyzer (but you can always execute “EXPLAIN (EXTENDED) SELECT …” from the SQLyog editor

    Please try out MONyog! MONyog can analyze queries in real time when connected to a server. Further analasis based on server logs (and a client side 'pseudo log') will be added soon.

    in reply to: #26199
    peterlaursen
    Participant

    We found the issue for the structure sync issue.

    http://dev.mysql.com/doc/refman/5.1/en/news-5-1-23.html says

    “It was not possible for client applications to distinguish between auto-set and auto-updated TIMESTAMP column values.

    To rectify this problem, a new ON_UPDATE_NOW_FLAG flag is set by Field_timestamp constructors whenever a column should be set to NOW on UPDATE, and the get_schema_column_record() function now reports whether a timestamp column is set to NOW on UPDATE. In addition, such columns now display on update CURRENT_TIMESTAMP in the Extra column in the output from SHOW COLUMNS. (Bug#30081)”

    and http://bugs.mysql.com/bug.php?id=30081 says (Jim Winstead is a MySQL developer)

    “It is not possible to tell, from the contents of the MYSQL_FIELD structure, whether a

    TIMESTAMP field will be set to CURRENT_TIMESTAMP on UPDATE. Connector/ODBC needs to be

    able to determine this in order to properly return results for the SQLSpecialColumns()

    ODBC function.”

    This change affects only 5.1.23. Not 5.1.22 and no 4.x, 5.0 or 6.x builds either (yet).

    We will have to take that change into consideration with structure sync (we execute SHOW FULL FIELDS from struct sync to get information about the tables involved).

    in reply to: #26175
    peterlaursen
    Participant

    Custom filters (on one or more columns) are planned for a future SQLyog ENTERPRISE release.

    We had actually started this, but allocated resources to Query Builder and Schema Designer.

    After 6.5 final release we will decide on next priorities.

    did you ever hear about a WHERE-clause … 🙂

    in reply to: #26203
    peterlaursen
    Participant

    We do not support that program version anymore. Please try the same with a recent version.

    But I think we never saw this. We will need a detailed testcase and details information about software versions (MySQL, WIndow) to reproduce it, if it still occurs with 6.15 and/or 6.5beta.

    in reply to: #26198
    peterlaursen
    Participant

    I don't see any problem with those two constructions not supported in GUI.

    We will check the dumps tomorrow!

    in reply to: #26196
    peterlaursen
    Participant

    to put it another way

    TIMESTAMP NOT NULL

    and

    TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP

    ..- is exactly the same in MySQL for the first NOT NULL TIMESTAMP in a table declared without an explicit default.

    in reply to: #26195
    peterlaursen
    Participant

    1)

    What do you mean “Yes, I see that this is indeed not possible, and never will be. Can't say I'm very pleased with that.” It IS possible. Please read the FAQ! Just check the 'Not Null' checkbox and that is it! The server will create a 'default CURRENT_TIMESTAMP on update 'CURRENT TIMESTAMP”.

    The first NOT NULL timestamp in a table is automatically CURRENT_TIMESTAMP on update 'CURRENT TIMESTAMP” unless some other default is declared. This is implemeted in the server like that for compability with versions before 4.1

    2)

    ……..

    3)

    Please provide a test case of two complete database structure-only DUMPS.

    in reply to: #26193
    peterlaursen
    Participant

    1) To define TIMESTAMP properties with SQLyog read

    http://webyog.com/faq/content/8/159/en/how…ith-sqlyog.html

    2) The 'coupled' checkboxes in structure sync GUI is a known issue (also reported some times before here). This will get our attention after 6.5 final. We will try to provide more 'fine grained' control of what can be sync'ed and not display checkboxes for object that cannot be synced independently

    3) I cannot reproduce reported problem with Structure Sync (6.5 beta1) and TIMESTAMPs. See attached.

    Both dabases has a single table like

    CREATE TABLE `tstest` (

    `id` int(11) NOT NULL default '0',

    `ts` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,

    `tx` varchar(30) NOT NULL default 'a',

    `bl` varchar(30) NOT NULL default 'b'

    ) ENGINE=MyISAM DEFAULT CHARSET=utf8

    Can you provide a test case: a structure dump for two databases to be compared?

    [attachment=860:not_here.jpg]

    in reply to: #26172
    peterlaursen
    Participant

    I do not know exactly, but almost sure that it is faster than using webserver extensions (PHP, ASP etc.). This involves communicating through a webserver and that must 'cost a lot' I think. But that would also very much depend on the environment, load and configuration and the host computer and that webserver.

    But I have no clue about how the performance of MySQL SP's compared to compiled binaries (most important C/C++), .NET (C#, VB.NET, J#), JAVA, common server scripting languages (Perl/Python/Lua ..).

    Actucally it would be funny to see some benchmarks of MySQL 'stored programs' examples compared to same functionality implemented in external apps/scripts using what connector is available. Problem is too that also the MySQL server as well as some of the connecors (the JAVA connector in particular) is highly configurable. It is definitely possible to set MySQL configuration parameters so low that it will hardly move, I think! So this exercise could very well become like 'at sælge elastik i metermål' as we say in Danish. (I think it translates to 'selling elastics by the metre'). You can set up such test to get what result you want to get! But waiting for your report anyway .. 🙄

Viewing 15 posts - 3,076 through 3,090 (of 7,398 total)