[peterlaursen]

here is a screenshot of mine

[peterlaursen]

A black line …

Thanks for the information! I think it could be a display problem then. What happens if you CHOOSE that black line (I think it represents the table although it does not display correctly). Do the icons on the right then color up ??

Could you provide a screenshot maybe.

I don't think there's anything wrong with you 🙄 but there is either with the beta or with your system …

[peterlaursen]

In the drown-down box that I pointed to with that big arrow, you choose your table, and the you can place the cursor in the pane, edit and save

[peterlaursen]

And – I just forgot to mention this point – the icons on the right of the drop-down-box change from grey to colored when you select the table.

[peterlaursen]

Well yes you can – but for security (I think) you must change the value in the drop-down-box form “noupdate” to “name of the table”. See attached pic …

[peterlaursen]

I have a table of about 35000 records and with sqlyog 4.05 beta2 updating is not slow (apprx. ½ second)

And that's true for the data-tab and the result-tab as well.

Could it be a graphics card/driver problem ?

Mine is a geforce 2 – mx and that's no “smart” card today ….

[peterlaursen]

Agreed

.. however I think it must be the fifth icon named “select some data for the table”. This one should show the data-tab.

The forth icon named “execute and edit resultset” should take you to the result-tab.

[peterlaursen]

Neither Windows with NTFS or LINUX with kernel version 2.4 or higher and Ext3FS have this file size limit.

But since Tom seems gone there is no use to discuss this matter ….

[peterlaursen]

Do you have an index/key that is (so) very long ??

There should be few problems with upgrading from Mysql 3.x to 4.0.x (it's worse with 4.1.x).

I have been looking for some server setting relatind to your problem but can't find it.

Can't find a setting in php.ini either …

I don't believe it's an sqlyog issue.

Did you try copying the sql from the history pane and execute it from for instance “My Sql Query Browser”.

Probably you'll get the same error message.

So my best guess is that the ISP haven't finished “trimming” their server parmetres yet. Did you contact then ?

[peterlaursen]

>> Shadow .. it's a myth and a very common misunderstanding!

From the mysql-documentation:

With the MyISAM storage engine in MySQL 3.23, the maximum table size was increased to 8 million terabytes (2 ^ 63 bytes).

But you will have to set the parametres for the table with the “create table” og “alter table” statement, since default is only about 4 GB.

[peterlaursen]

Any news here ?

[peterlaursen]

I almost (that means VERY!) sure that you have not ROOT privileges to a mysql database at an ISP, since that would give you )and everybody else with an account there) total control of the complete MySQL system !

At most you will have some “admin” privileges (after configuring an admin-user with the tool the the ISP offers – most probably phpMyAdmin)

Most often you must log on with “user_admin” or “mydomain_admin” or something like that … That would – with an appropiate webserver/mysql-configuration – give you full access to the databases that are yours and no other!

[peterlaursen]

I think you are almost there!

The message “unknown mysql host database.ispname.com” tells that that the tunnel php file actually is able to connect to the mysql system, but only the databasename is unknown.

So probably just should just supply your username as a prefix for the database like user_mydbname or something like that . Mine is looking like the pic below. It could also be that your ISP has more (physical) Mysql servers and you should supply a number lik 21″ in “mydb1”.

What is the connection string used by myphpadmin ? Should be the same!

All that information should be available from the “control panel” of your web account.

[peterlaursen]

Well – isn't that just “mawmaw” 😀

[peterlaursen]

Yes – I quote from the mysql documentation (some omitted)

*************************************************************

MySQL 3.22 had a 4GB (4 gigabyte) limit on table size. With the MyISAM storage engine in MySQL 3.23, the maximum table size was increased to 8 million terabytes (2 ^ 63 bytes). With this larger allowed table size, the maximum effective table size for MySQL databases is usually determined by operating system constraints on file sizes, not by MySQL internal limits.

The InnoDB storage engine maintains InnoDB tables within a tablespace that can be created from several files. This allows a table to exceed the maximum individual file size. The tablespace can include raw disk partitions, which allows extremely large tables. The maximum tablespace size is 64TB.

By default, MySQL creates MyISAM tables with an internal structure that allows a maximum size of about 4GB. You can check the maximum table size for a table with the SHOW TABLE STATUS statement or with myisamchk -dv tbl_name. See Section 13.5.4, “SHOW Syntax”.

If you need a MyISAM table that is larger than 4GB in size (and your operating system supports large files), the CREATE TABLE statement allows AVG_ROW_LENGTH and MAX_ROWS options. See Section 13.2.6, “CREATE TABLE Syntax”. You can also change these options with ALTER TABLE after the table has been created, to increase the table's maximum allowable size. See Section 13.2.2, “ALTER TABLE Syntax”.

******************************************

But before importing data to the table you should run the “alter table” statement with appropiate AVG_ROW_LENGTH and MAX_ROWS options as I wrote either from command line or from sqlyog.

[Author]

Posts