Ok, I think I've figured this out. From the examples I managed to find on the net, a "catch" tag is more like a try block than a catch block. I can't find any actual documentation that says that, but I infer that from the code I saw. I can use "j:if" to test for the exception afterwards.
> -----Original Message----- > From: Karr, David > Sent: Friday, July 21, 2006 10:52 AM > To: Jakarta Commons Users List; [EMAIL PROTECTED] > Subject: RE: Can Jelly SQL branch on table existence, or > error conditions? > > Where is an example of how to wrap a "sql:update" in a > try/catch? I found some limited examples by grepping the > core source tree (I can't find the source for the SQL tag > library anywhere), but I don't understand them. > > > -----Original Message----- > > From: Paul Libbrecht [mailto:[EMAIL PROTECTED] > > Sent: Friday, July 21, 2006 12:38 AM > > To: Jakarta Commons Users List > > Subject: Re: Can Jelly SQL branch on table existence, or error > > conditions? > > > > At worst the core's try/catch should help you, or ? > > Feel free to suggest added tags such as "tableAvailable" or > > "dbMetadata" > > or... > > paul > > > > Karr, David wrote: > > > I'm guessing the primary commons-user answerers are in a very > > > different time zone, so I guess I'm going to burst out a bunch of > > > questions, instead of waiting for answers for each one. > > > > > > In my Jelly SQL script, I'm going to need to drop and > > recreate a set > > > of tables. In order for this to work, it has to deal with any > > > variation of those tables existing or not. For instance, > > if the table > > > doesn't exist, dropping the table will fail in some way, so > > I'll need > > > to be able to ignore the error, perhaps. If I did this > > with plain sql > > > tasks in Ant, it will just fail the Ant script if the drop > > fails, and > > > I don't see how to get back info into the Ant script indicating > > > whether the table exists or not. > > > > > > Is this feasible in Jelly SQL? > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
