> On Tue, 2003-03-04 at 15:26, Eric D Nielsen wrote: > > The one place I haven't been able to use PostGreSQL to experiment is with > > regards to updateable views. I've found a few threads in -general and -hac > kers > > (including one linked from the ToDo list), but they all seem to die out wit > hout > > really reaching any sort of conclusion. I've also seen that in many > > cases it appears possible to use triggers/rules to simulate updateable view > s, > > but that feels like an inelegant solution to me. > > How so? A view is defined by ON SELECT rules; it seems natural, then, > that an updateable view would be defined ON INSERT / ON UPDATE rules. > AFAIK the only deficiency with the status quo is that the system does > not automatically define those insertion rules for you (in the subset of > cases where rules actually *can* be defined: for example, the view can't > include aggregation/grouping, calls to a user-defined function, etc.)
Using user-written rules seems inelegant to me because they force the user to do something the DBMS should be able to do itself. Should the rules be auto-generated by the DBMS then I wouldn't consider it inelegant. > If you'd like to work on getting PostgreSQL to make views updateable > automatically, that would be cool -- AFAIK no one else is currently > working on it. I'm definately willing to look into it, can anyone offer any advice for getting "situated" in the code? Are there paticular areas I should focus on understanding/areas I should be able to safely ignore? All my PostGreSQL experiences have been in user-land so far. Is there a good place to view the SQL99 standard without shelling out the $20 to ASNI? I know I'll have more questions later, but until then, happy coding... Eric ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
