Le Lundi 11 Février 2002 12:33, Gavin Sherry a écrit :
> The addition of trigger and rule/view
> recompilation is a convenience at best and there are alternatives to
> ALTER TABLE DROP COLUMN. Take a look at the TODO list: the most urgent
> items relate to replication/clustering, point-in-time recovery and
> row-reuse. All in all, it is these features which are much more desirably
> to current and prospective users.
Many projects ask users to vote for priority features.
Who can speak for end-users? Gavin, we need a pool in the to-do-list ...
These are hackers priorities which ***may** differ from end-user ones.
1) End-user point of view
My humble and personnal opinion, shared by many end-users, is that CREATE
TABLE AS (or whatever based on CREATE TABLE AS and UPDATE FROM) is not a
valid alternative. A database sysadmin with 500 tables, triggers and rules
cannot use alternatives. We need some basic features :
- to modify schema objects (CREATE OR REPLACE VIEW, CREATE OR REPLACE
TRIGGER).
- to drop schema objects (ALTER TABLE DROP COLUMN).
I would be very please if some users could express themselves. What is your
opinion as regards CREATE TABLE AS, ALTER TABLE DROP COLUMN, etc...
What is the end-user priority for such features in 7.3 ?
2) Use of libgda to query legacy databases
Would it be possible to add this feature in the the to-do-list (very low
priority = in the long run):
" use libgda to query legacy databases (Oracle, Sybase, MySQL) transparently
from PostgreSQL in order to access both data (tables, views) and schema
objects (triggers, functions, rules, types, etc..)".
Is this computer fiction to attach Oracle tables in PostgreSQL using libgda?
I can't tell and I would be happy to know the hackers' opinion.
Best regards,
Jean-Michel POURE
