[peterlaursen]

1) to create a database user needs CREATE privilege in MySQL. and to insert data he needs INSERT privilege. MySQL operates it own user privileges. It does not use the OS (Windows/Linux) user accounts. You can manage user accounts from SQLyog (5.2 supports all privileges)

2) if you create the back-up with the 'mysqldump' program it is stored on the server. If you use SQLyog it is stored on the client (or a network drive that is mapped to the client with a drive letter). However there is a small bug in SQLyog that can affect import of 'mysqldump' dumps (not dumps created with SQLyog itself). It is fixed in the beta tree. You can download latest (non-released) build from here http://www.webyog.com/downloads/betas/not_…SQLyog52Ent.exe if you need to import a 'mysqldump' dump with SQLyog (there is only a REGISTERED ENTERPRISE version as of now, but next beta will have the fix in all versions)

3) if you only want to copy some tables you can create the backup with SQLyog and you can select which tables to copy from the GUI – both the 'export tool' and the 'backup powertool' (actually you can with 'mysqldump' too – but the commandline can be a little tricky then!)). Actually you have also use the 'copy to other host' with SQLyog .. or use the DATA SYNC.

I think it is much easier if you experiment a little with non-important data!

[peterlaursen]

the reason for the error is that you must specify the lenth of a varchar.

A numeric and a decimal is the same! Sure that you would not like an INTEGER for the 'votes' ? And you would normally want some decimals available for 'rating' ?

About numeric types in MySQL:

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

I would also say that you should consider to have a Primary Key!

[peterlaursen]

Quote:

and datatype is set to “decimal”

did you specify the decimal format like decimal(19,4)?.

If you do not specify anything default is decimal(10,0)!

decimal is a 'high precision math type' in MySQL. It is good to use a decimal(x,4) for monetary data.

http://www.webyog.com/faq/29_90_en.html

[peterlaursen]

What is the SQLyog version?

Please

1) attach a screendump of the CREATE TABLE dialogue

2) copy the corresponding CREATE statement that fails from the HISTORY tab.

[peterlaursen]

You can install in any order. They are independent programs.

But SQLyog is not useful unless there is a server to connect to!

[peterlaursen]

The 'pre-beta5' with the fix:

http://www.webyog.com/downloads/betas/not_…SQLyog52Ent.exe

we only compiled the REGISTERED ENTERPRISE version.

[peterlaursen]

Quote:

NO_ZERO_DATE shouldn't conflict with the GUI and should be “honored” – in my opinion.

I do not disagree. It is the 'strict modes' that conflict with the GUI. We have not changed this since SQLyog 5.0, but maybe we should consider it somehow now.

[peterlaursen]

I think this answers your question:

http://www.webyog.com/faq/28_72_en.html

SQL_mode is a per-connection setting. SQLyog always uses the '' (empty) sql_mode for its connection.

You can check the HISTORY tab after connection has been established.

Maybe we should get the GLOBAL sql_mode(s) and use the ones that are not conflicting with GUI functionality. “NO_ZERO_DATE” is a good example.

A workaround could be to save a statement like ” set sql_mode = 'whatever you like' ” as a favorite and execute as first statement of your own.

[peterlaursen]

no issue …

.. but I can move it!

Manoj is working on a fix for this now. I hope I can put a link here to a 'pre-beta-5' in 1-2 hours.

[peterlaursen]

Quote:

show create function test

My 'ş ç ğ ı ü ö İ Ü Ö Ğ' characters showing '? ? ? ? ? ? ? ? ?'

I think this is not Sqlyog problem, its caming from MySQL. Thanks. I am sorry because of I must try before.

No I think it is a SQLyog issue. But starting from Beta4 we also have charset settings that are effective for RESULT tab.

[peterlaursen]

edit:

reproduced with beta4!

[peterlaursen]

Now ..

sorry for the confusion.

As I have written before SQL-import always creates a new connection. That is as expected.

We never had a similar report and never experienced this ourselves. We have now had a couple of SQLyogs inactive for a while and still cannot reproduce it.

Is it possible for us to get tempoarary access to the server?

Also do you have more SQLyog copies installed or only one?

If you have more has it happened on one PC only or more?

Could it be a specific server behaviour that triggers this?

A sort of memory corruption on your system?

Do you have an option to work on another computer?

Other ideas?

[peterlaursen]

MySQL 5.0.22 .. hmmm

OK .. we will certainly need to research into this.

Can you inform about time-out settings on the server?

For instance with a MySQL Administrator screenshot like this one.

But please upgrade SQLyog too.

[peterlaursen]

I am sorry but I had no intention of insulting anyone.

Please inform of you ever experience the same thing with beta 4.

I think I answered the support ticket (there was only one!).

[peterlaursen]

That is likely because you are not old enough!

1) A specific program verson or any?

2) I am old enough so I would like to see the data! Do something like copying a single or a few rows of data to its own table and export it: to create such table:

Code:

CREATE newtable SELECT * from … WHERE ….

[Author]

Posts