Re: [Firebird-devel] Re: XML Load/Dump Utility

[Jim S. <ja...@ne...>]

Alexander Klenin wrote:

>> The utility is built on the JDBC C++ binding defined in IscDbc. 
>
> How specific to Firebird is this tool then? Can it be used to 
> dump/load data from any JBDC-compatible database?
>
Funny you should ask.  It's completely general.  It should work against 
any database system that exports an JDBC/IscDbc compliant C++ API.  At 
the moment, there are two: Firebird and Netfrastructure.  If you'd like 
to use it against Netfrastructure, contact me off list and we'll talk!

> How do you determine the encoding? I think it sould at least be 
> controllable by the user.

By copying it out of a book.  I really haven't given it any thought.  If 
you have some ideas on what is required and how to handle various 
encodings, I'd like to hear about them.

>
>
>> The key questions, I think, are how data is presented. My starting 
>> point is:
>>
>>    * A table row is represented as a single xml element
>>    * Each non-null column is presented by an xml attribute
>
> I think that such a scheme is impossible to validate, at least with 
> DTD. This  is very unfortunate, but the only "correct" way IMO is
>   <row>
>     <column name="col1">data 1</column>
>     <column name="col2">more data</column>
>   </row>

Then don't validate the schema.  The purpose is to a) dump data from one 
database and b) restore it into another c) in a CVS friendly way.  As 
long as the grammatical rules of XML are observed, I don't see the 
theological problem as anything to get excited about.

> Yes, XML _is_ bloated :(
>
>> (I'm sending this as both text and html for readability. For those 
>> morally opposed to html mail, get a life.)
>
> I receive this list in a digest form, so I have to scroll through both 
> text and *undecoded* html versions of your e-mails. So while I think I 
> do have a life, it is not made any easier by this ;)

I'm sorry about that.  More intelligent list handling software would 
have prevented it.  I try to stay with straight text, but when 
formatting significantly clarifies the message, I want to be able to 
take advantage of it.  The SMTP mail format is designed for tools that 
can pick a rendering that it likes and ignore the rest.  It's a pity 
that the list server hasn't mastered MIME.

-- 

Jim Starkey
Netfrastructure, Inc.
978 526-1376