database transactions

Next topic

Author	Message
Brendan Pike	Tuesday 22 March 2005 10:54:17 pm In a development site I enabled InnoDB using the ezconvertmysqltabletype.php script. Interestingly it converted many non-eZ publish tables I was using inside the database also. For some reason a few eZ publish tables were not converted and continue to use MyISAM these are, ezcontentobject_tree, ezimagefile, eztrigger and ezurlalias. Is this intentional? www.dbinformatics.com.au We are always interested in hearing from experienced eZ PHP programmers and eZ template designers interested in contract work.
Frederik Holljen	Wednesday 23 March 2005 12:28:48 am Hi, I've notified the developer who made the script about this message (I unfortunately don't know the answer to your problem). He's left for eastern holidays however, so he won't be able to answer you until next week. Frederik
Brendan Pike	Wednesday 23 March 2005 5:38:53 am Thanks for the heads up Frederik I'll sit tight for now, I also found that trying to move a user to a new user group while editing the user results in a fatal error with a transaction related message. Although moving the user's location from outside the user works fine. Feels like a half implemented thing so I wont submit a bug report yet. www.dbinformatics.com.au We are always interested in hearing from experienced eZ PHP programmers and eZ template designers interested in contract work.
Raymond Bosman	Wednesday 30 March 2005 1:45:07 am Hi Brendan, Thanks for your notification. It was indeed not the intension to convert the non-eZ publish tables, which is fixed in the trunk. However it is not intentional to leave the tables: ezcontentobject_tree, ezimagefile, eztrigger, and ezurlalias unconverted. I discovered that MySQL crashes sometimes while converting a large table. Can you check your mysqld error log, to see whether this is the reason why some tables are skipped? You also found a bug while moving a user to a new user group. Probably the reason why this fatal error pops up is due to an invalid query. Without transactions the error would have been ignored. So can you report this bug, please? Thanks for your contribution, Raymond.