Bug #13570 | frederate table | ||
---|---|---|---|
Submitted: | 28 Sep 2005 14:16 | Modified: | 7 Oct 2005 9:53 |
Reporter: | Roberto Spadim (Basic Quality Contributor) | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Server | Severity: | S4 (Feature request) |
Version: | all | OS: | Any (all) |
Assigned to: | CPU Architecture: | Any |
[28 Sep 2005 14:16]
Roberto Spadim
[4 Oct 2005 18:15]
Jorge del Conde
Roberto, I'm not sure what you mean by this: "ALTER TABLE, CREATE TABLE, DROP TABLE, CREATE INDEX, DROP INDEX (we need know how to translate to another databases)" Can you please explain this to me ? Thanks!
[4 Oct 2005 19:23]
Roberto Spadim
for exemple, in sqlite we don't have alter table, but we can make some queries to workaround this, like wtcsqlite do, making federate tables to sqlite would know about this workarounds and make the same to port alter table drop table etc for sqlite
[7 Oct 2005 9:53]
Sergei Golubchik
It all could be done by the federated-sqlite storage engine (when it'll exist) - it'll translate ALTER to a sequence of commands, it'll accept CACHEABLE option in the CONNECT string.