Schema backwards compatibility

[Ivan Smahin]

Hello jda,

Friday, May 11, 2007, 6:30:11 PM, you wrote:

j> Hi Ruslan,

j> I just changed the schema of my database, adding 3 new fields. On 
j> opening older databases, my app modifies them to add these.

j> I was surprised to find that when I tried to open the new, modified 
j> db in the older version of my app it opened without a complaint! I 
j> checked with viSQL, and the database is indeed modified (has the 3 
j> new fields). Shouldn't the older version refuse to open it, 
j> generating a VException?

j> I'm quite happy to be able to open newer schemas with the older 
j> version of my app, but I didn't think it was supposed to work.

j> Using V2.5.8, BTW, and the API way for creating databases.

Are   you   expecting   some   exception   on   database.Open   using
"not-corresponding" objects structure defined in "static-way"?

I  just  don't understand why some app (even not yours) should not be
able to open db?

BTW,   SchemaVersion  might  be  used for this task.

-- 
Best regards,
Ivan Smahin 
Senior Software Engineer
Paradigma Software, Inc
Valentina - The Ultra-Fast Database
http://www.valentina-db.com