Thank you for your reply. Let me raise one or two more questions. Controller only understands "ANSI SQL 92". And, I am using the MySQLInnoDB dialect of Hibernate on my application. My concern is that the dialect may generate SQLs, not ANSI 92, and those requests may be in the pending list for ever.
The second question raises when one passes a MySQL dump file, generated from 'mysqldump' with the ANSI option, to Sequoia Console. When I tried to test with the ANSI converted dump, it was not successful, either. I am guessing that Sequoia might skip some of 'SET' statements in my ANSI dump file, or it might drop some of SET statements which is important to create tables and populate data, since it could not interpret SETs. I wonder how Sequoia deals with 'SET' statements in an ANSI dump file. Normally, SET statements deal with database dependent operations like setting UNICODE, or setting some restrictions in MySQL. Thank you for your reading. On Mon, Mar 23, 2009 at 4:43 PM, Emmanuel Cecchet <m...@frogthinker.org>wrote: > Hi, > > Sequoia sticks to ANSI SQL 92. > Consider all MySQL specific syntax and extensions as unsupported. > To bypass the loading problem, you can use the following procedure: > 1. shutdown Sequoia > 2. restore dump on 1st backend > 3. start Sequoia > 4. initialize cluster from 1st backend > 5. populate other backends using the standard backup/restore command of > Sequoia as described in the Sequoia documentation to initialize a cluster. > > Hope this helps, > Emmanuel > >> >> >> I am wondering which SQL version is completely compatible with Sequoia >> console and controller. The reason why I throw this question is that I tried >> to populate MySQL dump file (including schema and data) through Sequoia >> console, but it did not understand many SQL statements on it. I mean it only >> populated around 50% of tables and data. Other tables and data were failed >> because of syntax. >> >> If I want to populate the dump file, which is generated from MySQL, >> successfully to Sequoia console, which SQL version should I use? When I >> looked at the history, a couple of people already complained about this >> issue. But, it was not sure which version is exactly used in Sequoia. And, >> how much Sequoia understand the MySQL SQL syntax? >> >> And, is there any way to bypass MySQL SQLs up to the backends, without >> errors from the console or controller? Because, our system's backends are >> all MySQLs. >> >> Thanks you very much in advance. >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Sequoia mailing list >> Sequoia@lists.forge.continuent.org >> https://forge.continuent.org/mailman/listinfo/sequoia >> > > > -- > Emmanuel Cecchet > FTO @ Frog Thinker Open Source Development & Consulting > -- > Web: http://www.frogthinker.org > email: m...@frogthinker.org > Skype: emmanuel_cecchet > > _______________________________________________ > Sequoia mailing list > Sequoia@lists.forge.continuent.org > https://forge.continuent.org/mailman/listinfo/sequoia > -- 여호와는 네게 복을 주시고 너를 지키시기를 원하며 여호와는 그 얼굴을 네게 비추사 은혜 베푸시기를 원하며 여호와는 그 얼굴을 네게로 향하여 드사 평강 주시기를 원하노라 (민수기 6:24-26)
_______________________________________________ Sequoia mailing list Sequoia@lists.forge.continuent.org https://forge.continuent.org/mailman/listinfo/sequoia
