Re: [Dbmail] Mysql 2.2->3.0 Update Script

2012-02-14 Thread Reindl Harald
ERROR 1061 (42000) at line 262: Duplicate key name 'physmessage_id_2' because i cleaned up 'dbmail_envelope' and added the key to prevent get new duplicates until upgrade is done i would drop the whole table and re-create it attached a modified and overall

Re: [Dbmail] Mysql 2.2->3.0 Update Script

2012-02-14 Thread ITronic Harald Leithner
Now drops the index of the sievescripts table regardless of the name. Truncate the envelope table to prevent double key values. Harald Am 13.02.2012, 16:44 Uhr, schrieb ITronic Harald Leithner : schaut so aus... I have a key called owner_idnr_2 this key is a index on owner_idnr and name.

Re: [Dbmail] Mysql 2.2->3.0 Update Script

2012-02-13 Thread ITronic Harald Leithner
schaut so aus... I have a key called owner_idnr_2 this key is a index on owner_idnr and name. (looks like the update from 2.0 to 2.2). You have the same fields as unique key from 2.2.5 to 2.3.0 maybe the sql script should be changed to consider this. Am 13.02.2012, 16:27 Uhr, schrieb Reindl

Re: [Dbmail] Mysql 2.2->3.0 Update Script

2012-02-13 Thread Reindl Harald
AFAIK this is from Fedora 10/11 2009 maybe they have backported constraints which was originally not there and with not exactly the same name :-( dbmail_sievescripts | CREATE TABLE `dbmail_sievescripts` ( `owner_idnr` bigint(10) unsigned NOT NULL DEFAULT '0', `name` varchar(100) NOT NULL, `

Re: [Dbmail] Mysql 2.2->3.0 Update Script

2012-02-13 Thread ITronic Harald Leithner
Can you show me your create statement for dbmail_sievescripts? Am 13.02.2012, 16:06 Uhr, schrieb Reindl Harald : Am 13.02.2012 15:35, schrieb Paul J Stevens: On 02/13/2012 03:24 PM, Reindl Harald wrote: hi is there a really good reason dropping all foreign keys and create them new? this qu

Re: [Dbmail] Mysql 2.2->3.0 Update Script

2012-02-13 Thread Reindl Harald
Am 13.02.2012 15:35, schrieb Paul J Stevens: > On 02/13/2012 03:24 PM, Reindl Harald wrote: >> hi >> >> is there a really good reason dropping all foreign keys >> and create them new? this queries are running a very >> long time (i am testing your convert-sql this moment) > > > This script was

Re: [Dbmail] Mysql 2.2->3.0 Update Script

2012-02-13 Thread Paul J Stevens
On 02/13/2012 03:24 PM, Reindl Harald wrote: > hi > > is there a really good reason dropping all foreign keys > and create them new? this queries are running a very > long time (i am testing your convert-sql this moment) This script was changed to be more robust in the face of slightly different

Re: [Dbmail] Mysql 2.2->3.0 Update Script

2012-02-13 Thread Reindl Harald
hi is there a really good reason dropping all foreign keys and create them new? this queries are running a very long time (i am testing your convert-sql this moment) from me this feels a little to invasive, the last convertion took in summary 1 hour, i fear this would be increased a lot now | 2

Re: [Dbmail] Mysql 2.2->3.0 Update Script

2012-02-13 Thread ITronic Harald Leithner
Hi, I hope thats correct. Harald Am 11.02.2012, 21:12 Uhr, schrieb Paul J Stevens : On 02/10/2012 10:04 PM, ITronic Harald Leithner wrote: Hi, first there is an inconsistent in the create_table.sql and the upgrade 2_2-3_0.sql in create_table the some bigint columns are not unsigned for exam

Re: [Dbmail] Mysql 2.2->3.0 Update Script

2012-02-11 Thread Paul J Stevens
On 02/10/2012 10:04 PM, ITronic Harald Leithner wrote: > Hi, > > first there is an inconsistent in the create_table.sql and the upgrade > 2_2-3_0.sql > in create_table the some bigint columns are not unsigned for example: > part_id, physmessage_id, headername_id, headervalue_id > but in the upgrad