DataAssist and storage engines

How does Data Assist handle COMMIT with Innodb & MyIsam engines especially when different tables in a database are of both types?

I'm not so familiar with the COMMIT in regards to the engines for MySQL and the differences. DataAssist in general is using relatively simple SQL for inserts, updates, and deletes so I'm not sure if this would be relevant. Are you having some issue associated with this? As far as I know it is not going to treat one table differently based on the engine used, this would be an internal MySQL management issue.

Thanks Eric. We decided to start from scratch with a MySQL database that is totally utf-8 unicode. Do you know of any issues that we might face with Data Assist adn the other super suite products?

No issues with that setup that I can think of. I think UTF-8 is the way to go especially if you would like to have foreign character support within the db.

Thank you!

How does WA handle the need to use "mysql_query(’SET NAMES utf8′)"? We looked for it in some of the WA generated pages where we would expect to find it and we did not find any? Our MySQL database is all utf8 unicode, for a bit of background information.
Many thanks.

From what I have read about the SET NAMES this is an instruction that would be executed by a client connecting to a server to inform the server of the character set the data is being sent and what it should be returned as. If your db is all setup for UTF-8 and your charset on your pages is as well then you should not need to use this extra command since all the data will be UTF-8 anyway. One other thing that a colleague pointed out is that when you use UTF-8 the string searches performed will be case sensitive. This is different from using the latin-1 charset which is not case sensitive when doing searches. Here is a link to an article that discusses this:

case-sensitivity.html

Thank you. I suppose one can manually change the DA code to address the case sensitivity issue. Would you be kind to show me an example within a DA line of code (syntax) as opposed to the generic manual examples? Much appreciated.

This is more of just a notice that the db handles these types of searches differently. This is not something that you would be able to easily address in the DataAssist code directly. If you have issues with this when you get your search implemented let us know and we can look into your specific scenario to see if this is something we can account for.