[peterlaursen]

no there is no workaround! Sqlyog identifies the records by the PK. So wuthout a PK in the tabel you can't use Sqlyog.

If you're in control of the DB you could add an “autoincrement” integer/long type row to the table and make this one the PK.

[peterlaursen]

Are you sure that isn't just working ?

Current version of sqlyog isn't multithreaded, så you can't contact the program when it's working!

You don't tell whether the base(s) are on 'localhost' or on a remote server. In the latter case, you could try monitoring your network connection …

You also could try the syncronization wizard (yog 4.0 beta supports tunnellling so even if the server does not allow direct connection it should work.

Sorry if I didn't get the point !

[peterlaursen]

It has been said several times in this forum that a GUI for generating queries will be implemented with YOGMAX. A forms generator has not been mentioned as far as I know.

All that stuff should be Open Source in my opinion and should be available as a plugin for any program – such as Webyog, OpenOffice, MySQL Query Browser (ridiculous program!) and … and …

It's waste to have a dozen developer groups working on that and only each to produce a 75 % solution …. I've come across a few before reading about the one that you link to. I've been checking your link, and I'd prefer using Access as a frontend for MySQL through ODBC … It's a better GUI and though ACCESS is not particularly fast, it's faster than this one!

[peterlaursen]

And quite impressive PHP-code you've been writing 🙂

[peterlaursen]

sheer rubish I wrote last time …

Tunnel-sync is in my case aprox. 5 times slower than non-Tunnel-sync … (just made a rough measure) with same effective connection-speed.

probably becauxe the character-based XML transfer neeeds to transfer much more bytes the the binary C-interface does.

[peterlaursen]

just one remark about speed.

In my case the DSL-line is the bootleneck, so Tunnel-sync and common sync are actually equally fast in this case!

Any Idea about how fast af line you should have to have it make any difference with a “typical” MySQL/PHP-installation with an ISP/webhotel … ?

[peterlaursen]

OkieDokie .. This one Works …

Of course

1) “Tunnel” is with a big “T”

2) and tunneling (sorry …. Tunnelling 🙂 ) should be used only on the Server-side/target-side

[peterlaursen]

and the base used for this test is very simple.

It consists of one table with 8 fields: 5 varchars of different length and 3 doubles.

There is one (autoincrement) PK and one more unique index (varchar(255) that is a complete filename)

There is a little more than 30000 columns but I think that's not important …

[peterlaursen]

thanks for your patience … 🙂

I get the error message

(quote)

Sync started at Tue Sep 21 07:28:40 2004

Error fetching source server version information. Check the log file for more information.

Error No. 1

Error in tunneling XML file. Please contact [email protected].

(end og quote)

But the point is – I Think – that I'm not sure how to express the URL on the source-side.

I use “http://deepeter.dyndns.dk/SQLyogtunnel.php”

that is the root directory of a locally installed Apache server

(and yes, I copied the file to that position, and you can check for yourself!)

Source server version 4.1.3 (local), Destination server version 4.0.16 (web hotel)

Without tunneling sync works despite different server versions

[peterlaursen]

I just wonder: why do you store data permanently in .CSV-files?

Why not a table in a database ?

CSV-files are meant for backup and import/export purposes.

It's no problem to have two or more MySQL-servers on the network –

they just have to use different port-numbers.

I'm sorry if I missed the point!

[peterlaursen]

if the amount of data is not astronomic and if your are in possision of MSOffice you can consider another solution (that gives more control).

1)Read the text-data into Excel

2)Save as excel-datafile (.xls)

3) Create an empty database i MySQL using Sqlyog

4) Open the excel-datafile from Access

5) Export from Access via ODBC to Mysql

6) Correct tabledefinitions if necessary (for instance Mysql has much more text-types than Access) using sqlyog.

7) Create the indexes that you need and perhaps a primary key using sqlyog.

[peterlaursen]

totally uninteresting!

[peterlaursen]

I think not only “SQLyog appears to expand the size of “a” column to the byte length of the largest entry in “a” field” but the columnwill be as wide as the field definition in my experience.

But I'm still uncertain if I understand you right. Please upload a scrren-shot!

[peterlaursen]

Why don't you attach a screenshot? Its hard to know exactly what you are talking about !

[peterlaursen]

and it would be real nice if could brew coffee 😀

[Author]

Posts