[peterlaursen]

“I'm trying to do something seemingly simple in bringing a .txt file into a table.”

Are you using CSV-import with SQLyog?

Could you provide a small test case?

What are exact program versions?

There are no decimal numbers in your data?

[peterlaursen]

This is fixed in the 5.2 tree. The popup window is now 584 pixels wide and 530 pixels high (with 'normal' GDI setting)

[peterlaursen]

Just for information:

We spotted the reason that some of those crashes were 'silent crashes' and the dump code did not have effect. The reason was that we used some software to compress the executable. On WinXP that could destroy the new debugging funtionality.

Though a newer version of this compression software is available and does not seem to have this issue, we will stop using it – at least for a while.

[peterlaursen]

Just click the link reading 'SQLyog Enterprise 5.2 (BETA) Full' (this links to registered version)

[peterlaursen]

No. No way.

But do you mena parse for syntax errors only, or preview data changes?

[peterlaursen]

Ok … reproduced now.

For instance if you have a column named 'Id' (uppercase I) and use 'id' (lowercase i) in the query, it is reproducable. We will fix in RC1 probably later today.

[peterlaursen]

This column is an integer.

Do you have date exceeding the range as described here:

http://dev.mysql.com/doc/refman/5.0/en/numeric-types.html

“All integer types can have an optional (non-standard) attribute UNSIGNED. Unsigned values can be used when you want to allow only non-negative numbers in a column and you need a larger upper numeric range for the column. For example, if an INT column is UNSIGNED, the size of the column's range is the same but its endpoints shift from -2147483648 and 2147483647 up to 0 and 4294967295.”

You could then make it a BIGINT …

[peterlaursen]

It is planned as '2nd priority'. '1st priority' are the isuues planed for about 3 months from now. And after that comes 2nd priority.

[peterlaursen]

not reproducable here.

can you post the create statements and a query?

[peterlaursen]

Code:

create table `appTest` ( `applicationID` int (1) NOT NULL AUTO_INCREMENT, PRIMARY KEY ( `applicationID`));

..would be the normal SQL to use. No 'UNIQUE' keyword when 'PRIMARY' keword is used and a COMMA before 'PRIMARY'. I do not remember if there was such issue with this early beta, but please install beta 10! It works here.

[peterlaursen]

Just FYI:

We made a commeting mistake with this beta10, that can cause a crash from 'manage favorites'. This is located and fixed allready. This is an isolated issue and has no relation to what we discuss here.

[peterlaursen]

In the 5.2 tree we fixed the issue, that the program does not remember it MAXIMIZED state.

Now if it is maximized when closing, it will open as maximized next time.

[peterlaursen]

@TGKnight

Was that beta10 ?

[peterlaursen]

Did you ever read this article:

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

you will find that actually I too at that time requested a feature like

Quote:

WHERE source.blabla OPERATOR target.blabla

to be supported.

but the server does not understand 'soruce' and 'target'. SQLyog/SJA does not parse the WHERE clause. it is just sent to the server

The article also has a example of how you CAN use timestamps, however. And a 'trick' to use a server constant with the Primary Key.

You will find a few more Forums posts recently about similar issues. Actually we are discussing internally how to improve the usablilty of the DATA SYNC tool. We will udate this:

http://webyog.com/faq/33_20_en.html

when 5.2 FINAL is releases

[peterlaursen]

We should support this.

Now what is the SQLyog version that you are using?

Is it each and every database (in case you have more) where this is a problem?

What happens if you execute this SQL:

Code:

CREATE TABLE `aaaaa` (
`a` bigint(20) default NULL,
`b` bigint(20) default NULL)

You can see the SQL that generates the error in HISTORY tab. Please paste in a simple example that does not work.

[Author]

Posts