* the SQLyog version (and please update if version is not recent)
* was the SQL dump file created with SQLyog or another program? which one?
* From what server version did you export and to which did you import?
* SQLyog Connection type? direct, HTTP-tunnel or SSH-tunnel?
2) So please specify the exact meaning of 'crash'! Exactly what happens?
3) It SQLyog crashes it (with recent versions) will save a .dmp file in the data folder (and a messagebox will tell the name and postion of that file). Please zip and attach it here (it has no content that will compromise your privacy or data – only some code that makes it possble for us to identify the exact code position where it happens)
4) It would be great help if you could zip and attach a small example of such file that causes this 'crash' (note: .sql files must be zipped!). For privacy you can create a support ticket if you want.
5) Please confirm that this
Quote:
The database is still created and works fine, i just would like to know why it crashes when restoing the dump file
means that also all data (not only structure) were imported correctly before the crash occured?
In the 6.2 tree we plan to display only checkboxes for those objects that can be enabled/disabled individually. We also plan more detailed options for selecting what objects can be sync'ed.
Quote:
I would call this an essential feature and for an enterprise-class product, it should have been tested, just IMHO
It has been tested and documented, but not yet fixed. The current implementation goes back to early 2.x or 3.x versions (but not so visible at that time as only tables and no other objects were supported for MySQL databases at the time).
the option specify what columns are checked for identity. If you have a (set of) unique column(s) (more than the PK) you can specify thatthose one. You can avoid comparing large BLOB/TEXT columns byt specifying a subset of columns that can compared efficiently (small strings. numbers, date/time). This will reduce the amount of data processing on server side and client side as well.
I would also say that this “sync a table with source records 177000 and target records 28000 (approx.).” is not the optimal situation for SJA data sync. Unless you want to do a 2-way sync I would think you should copy thetable in the first place. After that schedule at intervals where up to 5-10-20% of rows (exact numbers depends on data) need some action.
The current situation will require lots of recursions/iterations to identify where action is needed.
In version 6.2 we will support export of individual Stored Procedures/Functions/Views/Events. After finalizing the 6.16 tree it will not take many days for 6.2 beta1 release.
This will be a COMMUNITY feature. But you are (always) welcome of course to evaluate the ENTERPRISE TRIAL!
what about using LIMIT? If I understand correctly this will be the same
Code:
UPDATE Products SET qty = '”+number+”' WHERE product_name = '”+prodname+”' AND
ID IN (SELECT ID FROM Products as p WHERE p.product_name = 'prodname' order by ID asc LIMIT 1
Author
Posts
Viewing 15 posts - 3,196 through 3,210 (of 7,398 total)