On Friday 15 June 2007 00:46, Oleg Bartunov wrote: > On Thu, 14 Jun 2007, Tom Lane wrote: > > [ thinks some more... ] If we revived the GENERATED AS patch, > > you could imagine computing tsvector columns via "GENERATED AS > > to_tsvector('english'::regconfig, big_text_col)" instead of a > > trigger, and then again you've got the dependency exposed where > > the system can see it. I don't wanna try to do that for 8.3, > > but it might be a good path to pursue in future, instead of assuming > > that triggers will be the way forevermore. > > > > Thoughts? > > No way with standard. GENERATED AS says that "all columns references in an > expression associated with a generated column must be to columns of the > base table containing that generated column." > > tsvector could be result of rather complex select involving several tables. >
Is there some reason for this restriction in the standard? I might be in favor of "extending" the standard to allow this case if not. -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org