Gang,
Ok, I will look into extending the Torque macros to add support at the
DB level via triggers. I am not sure it is possible, (it will depend on
what cross table access to the schema definition is available from the
velocity templates). BTW, it does not appear that commons-sql supports
MS S
On Dec 20, 2004, at 7:35 AM, Scott T. Weaver wrote:
I am getting the same thing now. We need to role back the SQL logic
to the point before the M1 release when this was not an issue.
If we role back the logic, then the cascading deletes will no longer
work leaving orphaned records requiring u
I am getting the same thing now. We need to role back the SQL logic to
the point before the M1 release when this was not an issue.
Randy Watler wrote:
David/Ate/Scott,
While executing the M1 scripts for DB configuration of MS SQL Server
2K, I ended up with these errors:
db.execute:
[echo]
I believe that changes to security-schema.xml on 12/3 just before the M1
release that included adding "on delete cascade" to these foreign keys
is what broke the MSSQL configuration for me. While I believe these
constraints are appropriate schema wise, I am afraid they are hitting a
MS SQL Serv
Guys,
Apparently, multiple foreign keys to a single related table with an ON
DELETE CASCADE constraint is not supported in MS SQL Server by design.
It requires use of yet another trigger to implement. Unfortunately, this
is not the first time I have been told to use a trigger for basic
constrai
David/Ate/Scott,
While executing the M1 scripts for DB configuration of MS SQL Server 2K,
I ended up with these errors:
db.execute:
[echo] Executing scripts for ./sql/DDL/mssql/security-schema.sql
[sql] Executing file:
/usr/share/tomcat5/jetspeed-database/scripts/sql/DDL/mssql/security-
