Hi,
Am I right in assuming that Dbo makes no particular provision
for the underlying database scheme to change ?
For instance, if I add another member to my class and add
the corresponding persist declaration and try and write
a record, the underlying database errors with:
[error] "Error during event handling: Sqlite 3: insert into ""record_name""
(""version"",
""field1"", ""field2"", ""field3"", ""field4"", ""field5"", ""field6"",
""field7"", ""field8"",
""field9"")
values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?): table user_account has no column named
field6"
Is there a recommended strategy to deal with schema migration ?
Thanks,
Graeme Gill.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest
