Hi Danny, since this is a common mistake with mysql: Are you sure that you want every message_id zeropadded up to 32 decimal digits? Thus you have a literal space of 10^32 numbers and a value space of only 2^32. The precision you apply to the integer column type denotes only the display precision not the precision of the value. A column of type integer is always 32 bit long. I know that this is of no importance in this context. Greetings, Marcus > -----Urspr�ngliche Nachricht----- > Von: Danny Angus [mailto:[EMAIL PROTECTED]] > Gesendet: Dienstag, 25. September 2001 15:32 > An: [EMAIL PROTECTED] > Betreff: RE: Bug in MySQL JDBC sqlResources table creation statement > > > Thats the confused conclusion I came to, > > however.. > a) it seems that a PK is needed by the JDBC driver, or the code. > and > b) it prevents duplicates corrupting the db > > but as the latest MySQL works with the SQL that > exists,(actually thats not > quite right, theres a typo in the PRIMARY () line.) my > preffered solution is > to recommend MySQL-3.23.42 or higher for this functionality. > After all its O.S. too, and easy to upgrade in-situ, so not a harsh > recommendation. > > d. > > > > > -----Original Message----- > > From: Serge Knystautas [mailto:[EMAIL PROTECTED]] > > > > Interesting. Do you really even need a primary key in this > case? Doesn't > > seem like you're using it. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
