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'
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:
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'.
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!
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.
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!
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.)
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.
Author
Posts
Viewing 15 posts - 3,346 through 3,360 (of 7,398 total)