db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Poeschl <mpoes...@marmot.at>
Subject Re: [PATCH] Fixes and enhancements for the sql2xml task
Date Fri, 29 Nov 2002 10:52:48 GMT
Andreou Andreas wrote:

> hi! I've only just starting following this list, and I was trying to 
> use the jdbc task in order to convert some of my databases
> (mainly oracle) to torque's xml. For some reason, this just does not 
> work for me, so I figured I could update the sql2xml
> task and have it generate the xml from my sql scripts. 

what was the problem with the jdbc task????

> So, the main changes are:
>    SQLScanner.java: now reports line number correctly on MS platforms, 
> and recognizes when the minus sign is not used for comments.
>    SQLToAppData.java: parses ALTER TABLE arguments, CREATE INDEX 
> statements and the CONSTRAINTS keyword in
>        CREATE TABLE. It now works ok for all my sql scripts+for the 
> scripts that get generated by torque (when given an xml)
>        The only problem I had was when a column was desclared as LONG 
> VARCHAR, which is easy to fix, but , since I'm new,
>        I don't know if we should support this type (maybe it's only 
> oracle specific).
>    Index.java-Foreign.java-Table.java: enable the previous changes + 
> now export xml fields that weren't exported
> I hope this can help those that want to convert sql scripts to xml. 
> Respect...

you only tested for oracle??

View raw message