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

Forum Replies Created

Viewing 15 posts - 3,346 through 3,360 (of 7,398 total)
  • Author
    Posts
  • in reply to: #25720
    peterlaursen
    Participant

    Bug confirmed!

    I am not sure what effect it has (do not know if the server uses this string at all).

    Anyway it is a bug and it will be fixed in next release!

    in reply to: #25693
    peterlaursen
    Participant

    OK …

    I think I understand that you define the column to have a 'required = YES' setting. This would be the normal way to define NUT NULL. Rather than using 'validation rules'

    With this there is a known bug with the ODBC driver reported here: http://support.microsoft.com/kb/124656

    Also with your file the ODBC driver reports “NULLABLE = TRUE”

    in reply to: #25692
    peterlaursen
    Participant

    Please tell: How do define the column *NOT NULL*?

    Do you use the 'validation rule' = 'is not NULL' ??

    in reply to: #25702
    peterlaursen
    Participant

    Warnings may not necessarily be a problem! the MySQL server sends lots of warnings. Some are important/critical and others are not necessarily!

    “Out of range value adjustment” occurs if data are adjusted to 'fit' the column definition. examples:

    * importing a negative number to a numerical column defined as UNSIGNED

    * strings truncated when they are too long.

    Also the server behaviour with warnings depends on the SQL_MODE (for recent server versions!)

    You will have to investigate the data after import and compare with source. Try a simple test case with a few rows of data to identify the problem.

    in reply to: #25704
    peterlaursen
    Participant

    Also the crash dump might be useful!

    in reply to: #25690
    peterlaursen
    Participant

    This we will have to check in detail on Monday. We have no other reports of this, but maybe only nobody else reported!

    Please:

    1) tell the SQLyog version you are using and the MySQL version you are importing to.

    2) it may speed up things a little if you attach a small sample .mdb file to reproduce with. One or two tables with only a few rows in each will do.

    Also if your SQLyog version is not the latest one, please try it! The TRIAL will work for such test as long as you only import two tables per job.

    in reply to: #25701
    peterlaursen
    Participant

    To run SQLyog on Linux you need to run it in Wine. There is no 'native' Linux version. Please refer to:

    http://webyog.com/faq/content/31/71/en/can…r-on-linux.html

    As regards performance it is hard to tell as there is nothing to compare with. Some applications (where both a Windows and Linux version exists) actually run faster on Wine compared to the 'native' Linux version. For other apps it is opposite.

    The Linux program you can download is not SQLyog but the SJA (SQLyog Job Agent). It is a command line utility containing a subset of the features of SQLyog Enterprise (data sync, backup, 'notifications service'). It does not require install. Just unpack with the 'tar' command (or some GUI unpacker) and call it from commandline with the jobfile as parameter. FAQs:

    http://webyog.com/faq/content/15/47/en/is-…or-windows.html

    http://webyog.com/faq/content/27/114/en/in…agent_-sja.html

    in reply to: #25698
    peterlaursen
    Participant

    I understand that this

    Code:
    to_email = 0
    is_sendmail = 1
    is_sendnoeventmail = [redacted]@pixar.com;[redacted]@pixar.com

    should be

    Code:
    to_email = [redacted]@pixar.com;[redacted]@pixar.com
    is_sendmail = 1
    is_sendnoeventmail = 0

    Please confirm that this is the correct and complete description of the problem!

    If you edit the file manually and restart MONyog it will work OK again?

    in reply to: #25677
    peterlaursen
    Participant

    1) currently no way. But you are right that executing the program from a removeable media is now broken. Let us discuss if some solution to this can be found. Maybe a startup parameter …

    2) I cannot promise any change in this in the foreseeable future. Anyway we always take users' opinion 'ad notam'.

    in reply to: #25689
    peterlaursen
    Participant

    I also have a comment to this:

    Quote:
    I used mysqldump with –all-databases option but it backedup only the first database because it had a view

    1) first of all: we are not responsible for what 'mysqldump' does!

    2) but I think that “backed up only the first database” should rather be “restored only the first database” ?? In my understanding it would be logical that way as the import will probably abort when encountering a non-existent user.

    If I am correct with 2) then pleae tell how you import. If you use SQLyog and execute as an external file job will abort on error. However you can copy/paste the file into the editor and 'execute all' and we will skip statements that return an error and proceed to next statement. But of course it should not be a DUMP that is GB's in size then!

    in reply to: #25688
    peterlaursen
    Participant

    The CREATE VIEW statement is how the view is defined on that server! Simply the returns of “SHOW CREATE VIEW”!

    In version 6.2 will plan to provide an option to remove ('strip out') DEFINER clause from VIEWS, SP's in exports, copy operations etc., so that definitions can be moved across servers with different 'user pool'.

    After 1-2 weeks we should be able to tell exactly how it will be implemented.

    in reply to: Bug: Export Table Data Also Exports View Data #23404
    peterlaursen
    Participant

    Just let me add that the 'workflow' of creating a table in the first place that is later replaced with a view is also used by the (autoritative) 'mysqldump' program. It is the ONLY way to ensure that VIEWs based on VIEWs will always import!

    in reply to: #25675
    peterlaursen
    Participant

    1) the .ini was moved to the Appdata Folder because of the security system of Windows Vista. On such system (with the default settings) a non-admin user does not have write access to the Program Files folder tree.

    2) you can continue using the PRO version you purchased at that time. For administrative reason (system maintenaince, transaction fees etc.) we cannot continue support for such low priced product. Also ENTERPRISE has grown considerably compared to COMMUNITY/PRO (Auto complete, Query Builder, Schema Designer etc.)

    in reply to: Bug: Export Table Data Also Exports View Data #23399
    peterlaursen
    Participant

    but this faq

    http://webyog.com/faq/content/17/78/en/wha…ation-tool.html

    .. seems not to have been updated with the information on VIEWs!

    in reply to: Bug: Export Table Data Also Exports View Data #23398
    peterlaursen
    Participant

    I do not not think these are the same issues!

    @PV:

    1) There is an option to export VIEWs or not (a checkbox). In 6.2 there will be a tree where you can 'pick' individual VIEWs.


    @Marc
    :

    You are using the term 'migrating', so I think you are using the Migration Tool? It is by design and documented as well that the Migration Tool will migrate VIEWs on theto TABLEs at the . Migration Tool is primarily designed for transferring data from non-MySQL databases to MySQL and a lot of users requested the option to migrate VIEWs onto TABLES on (it was not originally included in version 5.0 but added later following those requests). The code describing a VIEW is not the same on all those systems (what every one-year DBA should know too! 🙂 ) and we clearly documented that we do not attempt to 'translate' code from one database system to another. To transfer data from one MySQL server to another MySQL server there are several other options than the Migration Tool . For instance you can use structure sync and next sync data.

Viewing 15 posts - 3,346 through 3,360 (of 7,398 total)