BUG: Innodb, Assertion failure in file log0log.c with 4.0.!7

There is a MySQl/Innodb bug with Mysql-Max 4.0.17 on mac osx 10.3 panther. A google search showed a similar problem with another platform (I think it was windows). I am running 4.0.14 without any problems. After upgrading to 4.0.17, copying the data directory from 4.0.14 to 4.0.17 and then startin

JDBC driver: Buggy for DatabaseMetaData.getImported/Exported keys ?

Hi: I am using Connector/J 3.0.2 against MySQL 3.23.52-max. My default table type is set to InnoDB (since I always use innodb). The following methods are acting strangely: - DatabaseMetaData.getImportedKeys() - DatabaseMetaData.getExportedKeys() Often these methods return partial information

Re: JDBC J/Connect driver is seriously slow against InnoDB

Mark: Once of the great things about MySQL is the prompt attention and response on this list. Thanks for replying to this email so quickly. Read on... --- Mark Matthews <[EMAIL PROTECTED]> wrote: > j.random.programmer wrote: > > Hi: > > > > Thought I'd mention

JDBC J/Connect driver is seriously slow against InnoDB

Hi: Thought I'd mention this (using the latest dev J/connect): A) DatabaseMetaData.getColumns() does not return the last 4 columns (SCOPE_*) but it should according to the API spec B) InnoDB, on their benchmark page, say that inserting 100,000 rows into the DB is about 5 seconds. http://www.i

JDBC DBMetaData and proper FK rules against InnoDB tables

Hi: Consider (default table type set to InnoDb, mysql 3.23.52): CREATE TABLE A ( id INTEGER NOT NULL AUTO_INCREMENT, name VARCHAR(20), PRIMARY KEY (id) ); CREATE TABLE B ( id INTEGER NOT NULL AUTO_INCREMENT, AID INTEGER NOT

Re: InnoDB 3.23.52, foreign keys and update/cascade problem

Hi all: I'm seeing a strange problem updating a field if that field is referenced as a FK in another table. Consider: CREATE TABLE A ( id INTEGER NOT NULL AUTO_INCREMENT, name VARCHAR(20), PRIMARY KEY (id) ); CREATE TABLE B ( id INTEGER N

InnoDB 3.23.52, foreign keys and update/cascade problem

Hi all: I'm seeing a strange problem updating a field if that field is referenced as a FK in another table. Consider: CREATE TABLE A ( id INTEGER NOT NULL AUTO_INCREMENT, name VARCHAR(20), PRIMARY KEY (id) ); CREATE TABLE B ( id INTEGER N

A question about mm.mysql and the GPL

Hi: Firstly, I'd like to congratulate both MySQL AB and Mr. Mathews on making the JDBC driver an officialy supported download. I have a query though. Newer versions of the mm.mysql driver (now called connector/j) will be released *not* under the LGPL but under the GPL. Now if I am using the my

mysql daemon started asynchronously prevents logout - why ?

Hi all: I am running mysql-max 3.23.51 on linux 2.4.x and my shell is bash. The 'huponexit' shell option is off. The mysqld (mysql-max daemon) is probably not important for this discussion, any other daemon would do as well. Firstly, I can start mysqld (or other programs) asynchronously by sa

Re: Attn: MySQL AB: we need 3.23.5x NOW !

> We're running a custom-compiled 3.23.51 (or .52-pre, > [..] > Why not build your own? Hmm. The latest source on the pre-release page is 3.23.50 and it's not clear whether the "stability" issue is a bug in the code, the compiler or the runtime libs. > I can send you a binary that works for us.

Attn: MySQL AB: we need 3.23.5x NOW !

If any folks from MySQL AB are reading this: I need to go into production *today* with 3.23.5x. I am using InnoDB heavily (and need the newer fixes). 3.23.50 hasn't even been released yet (the pre-release version is not "stable") and based on posts on this list, we know that there are several bu

gcc for newer mysql versions - what's needed exactly ?

Hi all: Can someone (who knows this sort of thing) give a layman's introduction to the interplay between various gcc versions and various mysql versions (3.49, 3.50, 4.01 etc) ? I have some linux boxes and don't really want to have to install/use gcc 3.x (because then I have the hassle of multi

Re: Innodb tables lose foreign keys after creating an index...

--- Heikki Tuuri <[EMAIL PROTECTED]> wrote: > Rick, > > sorry, it is not mentioned in the manual that MySQL > performs a CREATE INDEX > by doing an ALTER TABLE. And ALTER TABLE has the > feature (= documented bug) > that it removes foreign key definitions. Heikki: Is there a fix planned for th

innodb, auto increment columns and gaps in the sequence - how to handle ?

Hi all: I have various mysql tables (innodb type) where I am inserting values in auto increment columns. The value inserted into the auto increment columns is null which automatically means that the table handler inserts the next higher value in that column. Problem is, many of these updates ar

innodb, auto increment columns and gaps in the sequence - how to handle ?

Hi all: I have various mysql tables (innodb type) where I am inserting values in auto increment columns. The value inserted into the auto increment columns is null which automatically means that the table handler inserts the next higher value in that column. Problem is, many of these updates ar

SQL/Design -- how to use sub entities/type discriminators ?

Hi all: Consider a hierarchy of users. All users have certain properties (they all have a name and date-of-birth). Additionally, based on their type, users have more properties. So a graduate user may have information regarding the year and school of graduation, a professor user may have informa