Use ";". Also, one may want to allow for some type of pluggable parser. For instance in the case of Oracle's PL/SQL you have nesting begin ... end for those cases it would be nice if the <sql> task performed the parsing on a separate function so a <plsql> task could be defined based on it.
Jose Alberto > -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 25, 2000 1:00 AM > To: [EMAIL PROTECTED] > Subject: Re: The new SQLExec task > > > >>>>> "CM" == Conor MacNeill <[EMAIL PROTECTED]> writes: > > >> (1) Remove the sql attribute and add a addText(String) method, > >> making the task accept #PCDATA. So > > CM> I actually added that bit so you could so things without needing > CM> an external file. No objections to you changing that. The > CM> semicolon processing is not presently part of the sql attribute > CM> handling so you would need to add that, > > I thought about moving the processing to a runStatements(Reader) > method that would be called with a FileReader or StringReader > depending on circumstances. > > CM> or have a nested element approach such as <sql> <statement> > CM> <statement> </sql> > > CM> This removes the delimiter processing which might be attractive. > > I have a strong RDBMS background and putting a ; at the end of my SQL > statements is more than natural for me - and you would need the > processing for files anyway. > > What do others think of this? > > Stefan >
