RE: Joined Delete

2008-04-11 Thread Thomas Fischer
Hi Carl, Thanks for the jira issue. The best thing that came into my mind as a quick solution is to select all objects you want to delete and to pass them one by one to XXXPeer.doDelete. This looks like a big performance issue but in fact it is not as Torque does this anyway internally :-(

AW: MSSQL JDBC2XML Task generates no XML

2008-04-11 Thread Thoralf Rickert
Okay, that was the problem. The schema must be dbo. My fault. Thanks Thoralf -Ursprüngliche Nachricht- Von: Thomas Fischer [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 10. April 2008 18:34 An: Apache Torque Users List Betreff: AW: MSSQL JDBC2XML Task generates no XML Did

Re: Joined Delete

2008-04-11 Thread Thomas Vandahl
Thomas Fischer wrote: The best thing that came into my mind as a quick solution is to select all objects you want to delete and to pass them one by one to XXXPeer.doDelete. This looks like a big performance issue but in fact it is not as Torque does this anyway internally :-( There is

Column names with spaces

2008-04-11 Thread Thoralf Rickert
Hi, Of course the list of problems with mssql doesn't stop... I've got now a xml schema from the existing database. Some lovely boy decided years ago that it would be nice to use spaces inside the column names of the database scheme. For example: Time after. This is not a problem if you use

RE: Column names with spaces

2008-04-11 Thread Thomas Fischer
This is going to be hard. Even if renaming the columns ist trouble, it is probably less trouble than getting torque to work with these column names. If you cannot change thecolumn names at all, all you can do is runnung your application and modifying all problematic parts you run into in the

RE: Column names with spaces

2008-04-11 Thread Greg Monroe
OK, short version: If you can't change the existing schema, use a view to get valid names. Longer version: Actually, the [ syntax is not the only one that can be used with MS SQL. It also supports the SQL Standard defined delimited identifiers. In the standard, normal identifiers (e.g.

AW: RE: Column names with spaces

2008-04-11 Thread Thoralf Rickert
Hi, Thanks for the answers. I think the View is the best solution for now. The changes to all the Base* classes and Base*Peers is not a problem, but the criteria and the generated sql commands don't like the spaces if it isn't escaped. bye Thoralf -Ursprüngliche Nachricht- Von: