>>
>> David Bayly wrote a very cool script in Frontier that takes the
>>following format as input:
>>
>> Customers
>> Customer
>> Name, string(30)
>> Address, string(50)
>> Photo, blob
>> Invoice
>> CustomerPTR, objectPtr(customer), deletionControl(delete_many)
>> Date, date
>> Total, float
>>
>> It might not be too much work to do a series of find/replace to
>>convert from one to the other. There's a free version of Frontier
>>5, and you don't need to learn much of Frontier to be able to run
>>David's script.
>>
>
>It would be easy enough to change the parser to read the mySQL
>format, but as Ruslan pointed out, the problem is how you map mySQL
>data types to Valentina data types. For example what is an id type in
>mySQL?
>
>And to make good use of objectPtr which have no analog in mySQL is a
>very big project.
>
Yes, it would if making a generic tool. However, it would be a reasonable
task if it is tool tailored for a specific project when one has a good
understand of the data and its structure and can define translation and
action tables. I have dealt enough with such conversions that I gave up on
a generic approach and create a custom tool for each project. Of course, I
do not have to start from scratch and in many instances the conversion tool
becomes a maintenance tool later on.
Robert
-------------------------------------------------------------
The Valentina mailing list is brought to you by MacServe.net
For info on lists services, see http://www.macserve.net/lists.html
©2000 Robert Brenstein |
