The result of this may be a need to change how we deploy/redeploy databases but
I will ask anyway
I have managed to get sequoia to work with our existing mysql databases
including it calls made to stored procedures which is great. I have yet to try
it on something other then my local box with more then one db but that is a
challenge for another day. Right now I am attempting to rework our seed scripts
to work through sequoia so when we redeploy and want to wipe the database we
can. I have taken out things like IF Exists calls (though it would be nice if
sequoia supported that) so I can recreate the tables fine. However when I start
on the stored procedures which change delimiter to $$ I get the following error:
org.continuent.sequoia.common.exceptions.driver.DriverSQLException: Message of
cause: Failed to execute request CREATE PROCEDURE XXX(IN... because of
(org.continuent.sequoia.controller.requests.StoredProcedure cannot be cast to
org.continuent.sequoia.controller.requests.AbstractWriteRequest)
Does this mean that sequoia cannot be used to reseed, or is there something
different I need to do with the seed sql?
I know I could just ignore the recreation of SPs and views but my concern is
that this is fine until one day we decide to change one.
I am looking for both short and long term solutions. So for example is their an
automated way I could get sequoia to rollback to the inital db state? If I have
changes to stored procedures is there a way without going through sequoia to
make the change that will not make sequoia unstable?
Thoughts? Options?
_________________________________________________________________
Send a smile, make someone laugh, have some fun! Start now!
http://www.freemessengeremoticons.ca/?icid=EMENCA122
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
