On Tue, 8 Jan 2008 05:11:44 -0800 (PST)
Andrzej <[EMAIL PROTECTED]> wrote:
> I achieved such a functionality/transparency already with an Oracle
> database using VIEWS and INSTEAD_OF triggers. But placing this in
> ORM would make it DB-independent what I actually need, as I'm moving
> from Oracle to PostgreSQL.
That seems the most reasonably way to solve the problem. Why can't you
do the same under PG? Doing all that work on the "client" side seems
very wrong anyway.
I don't know PG very well, but for example under Firebird you can have
"read/write" VIEWs appending an appropriate BEFORE
{EDIT/INSERT/DELETE} trigger that performs whatever you need...
ciao, lele.
--
nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
[EMAIL PROTECTED] | -- Fortunato Depero, 1929.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
