Jared,
The original column type is the same as that restored by Octopus. My
backends and controller are running on the same machine (different
ports). All running database backends are using the exact schemas.
For some reason, the type returned by the HSQLDB driver seems to be
different for the 2 database instances.
Could you use a SQL console such as iSQL or Squirrel to investigate the
database metadata returned by the HSQLDB driver and see if you get
exactly the same type values for the column in each database?
Looking at the code we have to compare the columns, they should have the
same name (but it seems to be the case) and have the same constraints.
Are you sure that the column has a unique constraint (e.g. pk
definition) in one db and not in the other one ?
Just a guess, but I tend to think that the Sequoia restore has problems
with duplicate name syntax for columns (in different tables).
This case should be properly dealt with. There might be some remaining
issues when using heterogeneous database engines reporting table or
column names with mixed cases but I think all of this is now properly
handled.
I really hope for a resolution since I am very close to using Sequoia as
our Cluster solution (assuming I can do a dynamic restore/enable).
If necessary, I hope you can implement a HSQL backuper as I have already
tried (quite unsuccessfully). :(
Are you running in a Linux or Windows environment?
Are your HSQL instances running on remote machine or on the same machine
as the controller?
Thanks for your feedback,
Emmanuel
--
Emmanuel Cecchet
Chief Architect, Continuent
Blog: http://emanux.blogspot.com/
Open source: http://www.continuent.org
Corporate: http://www.continuent.com
Skype: emmanuel_cecchet
Cell: +33 687 342 685
_______________________________________________
Sequoia mailing list
Sequoia@lists.forge.continuent.org
https://forge.continuent.org/mailman/listinfo/sequoia
