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
