Schema backwards compatibility

[Bart Pietercil]

Hi Jon,

If you can spare the time, I would appreciate some more info on this.
I must confess , I reread your question and still I haven't a clue  
what you are talking about


> Remember, I mentioned that my app uses the API way to creating a  
> db. Perhaps you don't use this, but if you do the schema of the db  
> you open must match the one defined in the db constructor.

Maybe I have a clue but my way of using the API might be different.

This is what I did

Make a new class based on VDatabase ValDB
in ValDB's constructor ---> call Super.VDatabase --for local dbs

Depending on what I need
then I call (no longer in the constructor) depending on situation  
createdb & deploy  or just opendb


Now I'm guessing but maybe you have your "deploy statements" already  
in the constructor of your class and "must" the schema you define in  
your constructor match the db you are opening ?



Of course , not urgent, but really appreciated

Thx

Bart
On 11-mei-07, at 18:27, jda wrote:

>>
>> Maybe I totally misunderstood you, but then again its friday  
>> afternoon and I worked hard :-)
>>
>
> Yes, I'm afraid you have totally misunderstood me.
>
> This has nothing to do with the schemaversion (which is just a  
> number). The actual schema has changed (more fields). Yet the older  
> version of Valentina, whose schema no longer matches the new one,  
> still opens the db without giving a VException. This has never  
> worked like this in the past.
>
> Remember, I mentioned that my app uses the API way to creating a  
> db. Perhaps you don't use this, but if you do the schema of the db  
> you open must match the one defined in the db constructor.
>
> Ruslan, can you comment?
>
> Jon
> _______________________________________________
> Valentina mailing list
> Valentina at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina