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

Forum Replies Created

Viewing 15 posts - 3,196 through 3,210 (of 7,398 total)
  • Author
    Posts
  • in reply to: #25667
    peterlaursen
    Participant

    I have no option to check from here, but I understood that this was fixed in the final 6.16 release.

    Would you mind verify this?

    in reply to: #25988
    peterlaursen
    Participant

    1) Please tell

    * 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 reply to: #25984
    peterlaursen
    Participant

    ok .. now I got your point!

    We should display something like “showing x rows of total y”, right?

    Request added here: http://code.google.com/p/sqlyog/issues/detail?id=564

    in reply to: #25987
    peterlaursen
    Participant

    This is a known issue. It is reported to our issue tracker http://code.google.com/p/sqlyog/issues/det…tructure%20sync (even though you might describe it otherwise)

    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).

    in reply to: #25982
    peterlaursen
    Participant

    Please see attached. For me it displays '7 rows' for that table in the status bar (6.16 RC2).

    [attachment=839:rows.jpg]

    in reply to: #25971
    peterlaursen
    Participant

    I think it was in the paper but anyway:

    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.

    in reply to: #25972
    peterlaursen
    Participant

    What is the program version?

    The files used by 'autocomplete' were stored in the 'program files' folder tree before 6.07. From 6.07 it will use user's 'application data' folder.

    This is not settable. We did no think that was required!

    Does this 'profile limitation' apply to 'program files' folder tree or user' s 'application data' folder or both?

    9 MB is really not much storage nowadays where every decent PC ships with a 250+ GB harddisk!

    in reply to: #25967
    peterlaursen
    Participant

    I don't know if you can copy from that table.

    If it works it is undocumented, and I would not recommend.

    At least I think server versions should be identical.

    in reply to: #25969
    peterlaursen
    Participant

    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 reply to: #25968
    peterlaursen
    Participant

    what is happening.

    It is generating checksums on 'chunks' of rows (recursively) to identify what rows need to be inserted/updated(deleted.

    Please refer to this FAQ:

    http://webyog.com/faq/content/11/61/en/how…ation-tool.html

    additional resource:

    http://webyog.com/en/whitepapers/Using_SQL…L_Databases.pdf

    think about if you could possible use the optimization option!

    in reply to: #25965
    peterlaursen
    Participant

    workaround:

    select the SP in the Object Browser and copy the CREATE statement to clipboard (Ctrl-C) from the OBJECTS tab.

    in reply to: #25964
    peterlaursen
    Participant

    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!

    in reply to: #25880
    peterlaursen
    Participant

    sorry .. this was not the correct test case.

    I reported this bug

    http://bugs.mysql.com/bug.php?id=34731

    .. that I am pretty sure about!

    in reply to: #25665
    peterlaursen
    Participant

    Not reproducable on my (Vista) system.

    This we will look into!

    in reply to: #25963
    peterlaursen
    Participant

    I found this SQL Server doc

    http://msdn2.microsoft.com/en-us/library/ms189463.aspx

    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
Viewing 15 posts - 3,196 through 3,210 (of 7,398 total)