You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by Martin Poeschl <mp...@marmot.at> on 2003/06/20 10:58:56 UTC
[SOURCE] Issue #TRQS121 modified
You can view the issue detail at the following URL:
http://scarab.werken.com/issues/id/TRQS121
Type
Defect
Issue ID
TRQS121 (native limit and offset breaks on postgresql 7.3)
Modified by
Martin Poeschl
mpoeschl (mpoeschl@marmot.at)
The following modifications were made to this issue:
---------------------------------------------------------------------
Status changed from 'New' to 'Closed'
Resolution set to 'Fixed'
Reason:
fixed in HEAD and 3_0_BRANCH
---------------------------------------------------------------------
This message is automatically generated by the Scarab
issue tracking system. For more information:
http://scarab.tigris.org/
Re: [SOURCE] Issue #TRQS121 modified
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
"Alexander Fedorenko" <af...@informex.net> writes:
-1
Make this configureable by the XML file. Changing this behaviour would
seriously upset applications which rely on getting an Exception when a
row is removed that is referenced from another table.
But the default should be as it is. Throw an exception if there is a
referential problem.
If you're interested in your table behaving like you described, you
should look at the "ON DELETE CASCADE" constraint for your
column. Martin, can we somehow supply such a constraint for the
templating engine?
Regards
Henning
>Hello.
>Very good.
>And just another small thing
>2. DROP TABLE command
> ... from PostgreSQL documentation
> DROP TABLE always removes any indexes, rules, triggers, and
>constraints that exist for the target table. However, to drop a table
>that is referenced by a foreign-key constraint of another table, CASCADE
>must be specified. (CASCADE will remove the foreign-key constraint, not
>the other table itself.)
>Code in file src\templates\sql\base\postgresql\drop.vm
>DROP TABLE $table.Name;
>Should be replaced with
>DROP TABLE $table.Name CASCADE ;
>-----Original Message-----
>From: Martin Poeschl [mailto:mpoeschl@marmot.at]
>Sent: Friday, June 20, 2003 11:59 AM
>To: Bill Schneider
>Cc: torque-dev@db.apache.org
>Subject: [SOURCE] Issue #TRQS121 modified
>You can view the issue detail at the following URL:
> http://scarab.werken.com/issues/id/TRQS121
>Type
> Defect
>Issue ID
> TRQS121 (native limit and offset breaks on postgresql 7.3)
>Modified by
> Martin Poeschl
> mpoeschl (mpoeschl@marmot.at)
>The following modifications were made to this issue:
>---------------------------------------------------------------------
>Status changed from 'New' to 'Closed'
>Resolution set to 'Fixed'
>Reason:
>fixed in HEAD and 3_0_BRANCH
>---------------------------------------------------------------------
>This message is automatically generated by the Scarab
>issue tracking system. For more information:
>http://scarab.tigris.org/
>---------------------------------------------------------------------
>To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
>For additional commands, e-mail: torque-dev-help@db.apache.org
>---------------------------------------------------------------------
>To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
>For additional commands, e-mail: torque-dev-help@db.apache.org
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
RE: [SOURCE] Issue #TRQS121 modified
Posted by Alexander Fedorenko <af...@informex.net>.
Hello.
Very good.
And just another small thing
2. DROP TABLE command
... from PostgreSQL documentation
DROP TABLE always removes any indexes, rules, triggers, and
constraints that exist for the target table. However, to drop a table
that is referenced by a foreign-key constraint of another table, CASCADE
must be specified. (CASCADE will remove the foreign-key constraint, not
the other table itself.)
Code in file src\templates\sql\base\postgresql\drop.vm
DROP TABLE $table.Name;
Should be replaced with
DROP TABLE $table.Name CASCADE ;
-----Original Message-----
From: Martin Poeschl [mailto:mpoeschl@marmot.at]
Sent: Friday, June 20, 2003 11:59 AM
To: Bill Schneider
Cc: torque-dev@db.apache.org
Subject: [SOURCE] Issue #TRQS121 modified
You can view the issue detail at the following URL:
http://scarab.werken.com/issues/id/TRQS121
Type
Defect
Issue ID
TRQS121 (native limit and offset breaks on postgresql 7.3)
Modified by
Martin Poeschl
mpoeschl (mpoeschl@marmot.at)
The following modifications were made to this issue:
---------------------------------------------------------------------
Status changed from 'New' to 'Closed'
Resolution set to 'Fixed'
Reason:
fixed in HEAD and 3_0_BRANCH
---------------------------------------------------------------------
This message is automatically generated by the Scarab
issue tracking system. For more information:
http://scarab.tigris.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org