[peterlaursen]

The reason for this could be that the GRANT tables “belong to” a another MySQL version than the one that you are using.

What is your MySQL server version ? Has this version been installed over an older version ? (which ?). Or has the DATADIR (or worse: part of it!) been copied from another mySQL installation ?

[peterlaursen]

no bad feelings …

the point is that a tinyint works fine and seamlessly as a boolean, so if you use like that you just don't think about it after a while … 😀

[peterlaursen]

Ritesh was not right …

.. but as I wrote it is commonly used to use a tinyint as a substitute for a boolean. With a tinyint you can for instance use values -1, 0 and 1, and that gives the opportunity to let -1 have a special meaning.

One appplication that makes use of this is the popular forum software phpbb2. With the config-table of this application 1 means true, 0 means false and -1 means “use defaults”. I believe that this also is a “workaround” that is used by this software so that it will run with the same code on more database-server systems.

But a tinyint(4) is NOT a boolean. Value could be “-127” ….

[peterlaursen]

Is the DB and table existing ??

If not you must include CREATE statement for the DB and the table.

[peterlaursen]

I just did a simple test with 48 bit PNG's…

They import and export OK, but they don't display as graphics in the viewer.

I tried to attach a 48 bit PNG here but it says “You cannot upload this type of file”. I could mail you a few ones if you want ??

[peterlaursen]

@Ritesh:

will it work with 48-bit and 96-bit PNG's ?

[peterlaursen]

Wrong Ritesh!

See

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

Tinyint is a 1-byte integer, ie. it ranges from -128 to 127

Tinyint(1) is wide used a a replacement for a boolean and the ability to set it for instance (-1) can be very usefull. But it IS not a boolean!

did you confuse it with a “bit” type ?

“As of MySQL 5.0.3, a BIT data type is available for storing bit-field values. (Before 5.0.3, MySQL interprets BIT as TINYINT(1).) In MySQL 5.0.3, BIT is supported only for MyISAM. MySQL 5.0.5 extends BIT support to MEMORY, InnoDB, and BDB.”

[peterlaursen]

the TIF's and PNG's are they

1) 24 bit images (8 bits pr. channel)

or

2) 48 bit images (16 bits pr. channel) ?

If you have a “better” digital camera the image-chip records the image with 12 bits/channel. If you transfer the RAW-images to your computer (instead of using the camera's RAW >> JPG conversion program – the so-called “image processor”) and convert the RAW's to TIF og PNG the “better” programs (such as Adobe Photoshop CS and CS2) will convert to the 48-bit version (unless you set it to make 24 bit formats) in order not to throw information away. PNG's and TIF's support 48 bit format – JPG's and GIF's don't

(actually with Photoshop CS2 you can make 96 bit (32 bit / channel) TIF's and PNG's).

I think that the BLOB-viewer in SQLyog will only work with 24 bit formats, so if that's not what you got, that could be the explanation.

I would like to repeat here that the BLOB-viewer should support the use of GNU GTK graphics library (the one that is use by the GIMP) as a plugin. Image formats develop so rapidly today with the developments in digital photography that it is not realistic that a company like webyog – that are database specialists, not graphics specialists – will be able to cover the developments in a satisfying way. And why waste time writing code that's freely available in better quality than you would ever be able to do yourself ?!

[peterlaursen]

If you understand, that you must “unfold” the browser tree by clicking the “+” with the mouse, it sounds pretty strange!

I doubt this is an issue with SQLyog. Did you try other clients ? “MySQL Administrator” or “MySQL Query Browser” for instance ?

1)

Try pressing the “refresh”-button after connection is established (it's the one with the “recycle”-symbol)

2)

Also try issuing this SQL from the SQL-pane in SQLyog “show tables from my_db” with one of the blank databases as “my_db”` Do you get any eror message with that ?

[peterlaursen]

I don't think it' common that you should use a prefix with each table – just the database and the user(s)

[peterlaursen]

you must configure an ODBC-instance! (from “administrative tools” in control panel)

If you want to IMPORT from Ms-Access using Sqlyog's “powertools” it must be an instance of the Microsoft Driver for Access. It could be a “system-DSN” or “user-DSN” and should point to the Access databasefile.

If you want to EXPORT from MS-Access, the ODBC-driver to configure must be the ODBC-driver for MySQL, that you can get from http://www.mysql.com. And it must be configured with a “connection string” (server-URL, User and password) that describes the MySQL-connection

MySQL also has an ODBC-import-tool. Never tried it because it crashes on my computer!

Using Sqlyog and importing from here is more flexible than exporting from Access. When the Access-driver is correctyly configured the name of the ODBC-instance will be visible in the drop-down-box in the Sqlyog ODBC-import wizard.

Are you sure you understand ODBC ?

[peterlaursen]

@ Ritesh

Her is your screen-dump!

Chosing One DB in the object browser and ANOTHER in the export dialogue generates this eror!

[peterlaursen]

OK I can reproduce it now just like …

Code:

/*
SQLyog Enterprise v4.06 RC1
Host – 5.0.6-beta-nt-max : Database – test
*********************************************************************
Server version : 5.0.6-beta-nt-max
*/

create database if not exists `test`;

USE `test`;

Now you write

Quote:

When I choose the DB I want to sqldump before I select the menu item it´s ok.

It´s just when I select another DB in the sql dump screen that I get this error.

That makes things perfectly clear! I did not get that point until now. I always sqldump from right-clicking on a DB or a table, so I never ran into it myself!

Well .. yes … it must be categorized as an error with the program … but not critical for me.

[peterlaursen]

Yes but Shadow … that was not the question. Since he can connect from machines on the “outer ” side of the router user accounts with the MySQL server are OK.

But with computers behind the router he gets redirected to to “localhost”. That's a local network problem and has nothing to do with neither the MySQL server nor with SQLyog. The only way I know this redirection could take place is to put a line like this in the hosts-file

127.0.0.1 domain.tld (tld = top level domain like 'com')

The hosts-file is located somewhere like c:windowssystem32driversetc

(But with certain type of network setup they might be other reasons for this redirection).

I suggest “real IP” is “global IP”. That makes sense – he can connect to the remost MySQL server fram machines that have a “global IP” but not from anotehr has has no “global IP” – ie. computers that are behind a router (and thus have only a “local IP”).

[peterlaursen]

There should be no problem in connecting to a remote server!

And it probably is the same problem with Other clients ?

What are the details that you provide on the connection screen ? The same on all machines ?

A very special situation could be if your hosts-files redirects the URL of the remote MySQL-server to “localhost”. A rason for that could be that the network admin does not want computeres behind the gateway(router) to connect to the remote server.

😎

[Author]

Posts