Dealing with a change in language/encoding

[Ruslan Zasukhin]

on 4/12/03 2:56 PM, jda at jda at his.com wrote:

>> This operation -- "change of Language" -- is operation that modify db
>> structure.
>> 
>> Therefore, you need Upgrade your databases to __new__ version of
>>    
>>     Db.SchemaVersion
>> 
>> You do not need import/export.
>> 
>> You need just do correct steps with SchemaVersion.
>> 
> 
> SchemaVersion is just a number that we (the developer) uses for their
> own tracking purposes, right?.

yes

> Are you saying that Valentina will
> modify the db structure automatically when the old db is opened, but
> that we are responsible for making sure that the schemaVersion
> (assuming we use it) is modified accordingly?

No, YOU must check SchemaVersion of db on open, and if you see that it is
old, YOU must modify db, change SchemaVersion

> In other words, I think
> you are saying that there is nothing we explicitly that we have to do
> to convert between languages/encodings. Sorry to be slow, but is that
> right?

-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://listserv.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------