Is anybody still using the ability to set sql_inheritance to OFF?
I'm considering removing the parameter in PG 8.3, so that the current
default behavior (sql_inheritance = ON) would be the only behavior.
sql_inheritance was created in 7.1 to allow existing applications to
not be broken when we
So: would anyone cry if sql_inheritance disappeared in 8.3?
+1
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
+1;
Tom:
I regularly use the inheritance features of postgreSQL -- Probably 25% of my
schemas rely on it for the techiques I use such as: history tables,
recursion tables [parent-child and trees], among others.
What is the potential impact for the ONLY qualifier ??? None I would
expect, as
Ron Johnson [EMAIL PROTECTED] writes:
On 03/21/07 09:49, Tom Lane wrote:
Is anybody still using the ability to set sql_inheritance to OFF?
Shouldn't features be deprecated for a version before removal?
Effectively, that feature's been deprecated since 7.1 ...
regards,
codeWarrior [EMAIL PROTECTED] writes:
What is the potential impact for the ONLY qualifier ??? None I would
expect, as the ONLY qualifier effectively sets SQL_INHERITANCE = off for
that specific query --
What about decorated table names: i.e: SELECT * FROM cities* ??? Do we
get to keep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/21/07 11:13, Tom Lane wrote:
Ron Johnson [EMAIL PROTECTED] writes:
On 03/21/07 09:49, Tom Lane wrote:
Is anybody still using the ability to set sql_inheritance to OFF?
Shouldn't features be deprecated for a version before removal?
