On Fri, Feb 11, 2005 at 08:12:50PM -0500, Milla Erdee wrote:
You have BYTEA and TEXT which fill this need. But you could add CLOB and BLOB types as synonyms for BYTEA and TEXT just to ease converting code written for other RDBMS.
Also, has PostgreSQL considered adding some CLOB and BLOB types?
Has had these for ages.
The updating view syntax in many cases might be preferred in certian cases and other types of syntax in other cases, and it should be up to the programmer to decide which is best for a certian application.. A certian syntax might be best for a certian case but another might be best for another case. By the way, Updating views is where you can update a table with INSERT, DELETE, UPDATE etc through a view.
Updating Views
You can create RULEs to do this.
They would add additional functionality in case this kind of flexibility is determined to be needed. Another idea: triggers on SELECTs. Why not? Triggers can be useful for many more things than their original use.
Triggers on Views
What would they do?
Additional Trigger Syntax (ie Oracle):
I'm not seeing anything there more than syntactic sugar that PostgreSQL doesn't support, but no, it doesn't take that syntax.
Then why not go ahead and support it, since it would seem it wouldnt be difficult. I dont think PostGRESQL supports INSTEAD OF triggers as well.
Generally I think that it is a good idea to follow the philosophy where we realise that just because a feature has no apparent benefit or use for us, that no one else will need it. A feature that may have no use for one person might be essential to another person. I believe it is important to not place arbitrary restrictions or restrictions based on personal preferences on how software can be used, for the reason I just stated.
---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
