Automatic Data Entry

[Ruslan Zasukhin]

On 10/28/04 11:26 AM, "Peter De Berdt" <peter.de.berdt at pandora.be> wrote:

>>> I don't know how the Valentina plug-in handles things (and I don't
>>> have
>>> a problem with maintaining a correct database structure myself, my
>>> classes handle this), but let me give you an example:
>>> 
>>> SchemaVersion 1
>>> MyVDatabase
>>>      -> MyBaseObject1
>>>          € MyField1 as VVarchar
>>>          € MyField2 as VULong
>>>          € MyField3 as VDouble
>>> 
>>> SchemaVersion 2
>>> MyVDatabase
>>>      -> MyBaseObject1
>>>          € MyField1 as VVarchar
>>>          € MyField2 as VLong
>>>          € MyField3 as VDouble
>>>          € MyField4 as VString
>>> 
>>> What you have to do now, is before creating an instance of
>>> MyVDatabase,
>>> open up that database as a generic VDatabase, then create the new
>>> field, alter the type of MyField2, then close the database again,
>>> instantiate a MyVDatabase and then start working with your database.
>> 
>> But instance we create BEFORE do open
>> 
>>     db = new myDatabase
>> 
> Wouldn't it be possible to check the database file on opening then?

Let's' think.

You have made example only of ONE simple change.
* adding of new field.

--- YES I think such change we can catch.

What about other changes:

* remove of field
* rename of field
* change of type
* change of flags
* change of constraints

* add of table
* remove of table
* change table name



-- 
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://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------