Re: [DOCS] [PATCHES] "ALSO" keyword to "CREATE RULE" patch
Fabien COELHO wrote: > > Dear Bruce, > > > Is ALSO part of the SQL standard? I can't imagine it is because there > > is no rule mention. > > As RULE is not in the SQL standard, ALSO is sure no part of it. > > > I guess if we were coding from scratch, we could make the syntax INSTEAD > > or ALSO, but at this point, I don't see adding ALSO as a useful change. > > It depends on what you mean by "useful". It is certainly non essential. > I just think it is "user-friendly". > > It took me some time to understand that rules were appended by default. > With the "ALSO" keyword it would have been instantaneous. > > When I first looked at the syntax with the "INSTEAD" which is optionnal > and without alternative, I thought that it was one of those useless > keywords that are allowed so as to make SQL more English-like, as the > "COLUMN" keyword in the ALTER TABLE syntax. You may argue that I did > not read the documentation in depth, but I'm not sure I'm the only one;-) > > The change is very small (2 lines added, 2 lines changed), and upward > compatible, provided that the user has not used ALSO as an object name, > what seems rather unlikely IMVVHO. > > Most of the patch deals with the documentation, which is rather ugly > because it keeps telling about "INSTEAD" vs "non-INSTEAD" rules, as there > is no name for the default behavior. I think "ALSO" fixes this issue as it > clarifies the explanations. Actually, our real problem is that the INSTEAD keyword wasn't mentioned as part of instead rules (second paragraph), and there was no mention of INSTEAD in the parameter section. I just fixed this in current CVS: http://candle.pha.pa.us/main/writings/pgsql/sgml/sql-createrule.html This should prevent misunderstanding in the future without adding an additional keyword. If we were starting from scratch, we would perhaps require either ALSO or INSTEAD, but since we already have existing users, clarifiying it seems better. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [DOCS] Request temporary freeze of libpgtcl chapter in manual
On Wednesday 03 March 2004 21:30, L J Bayuk wrote:
> Henry B. Hotz wrote:
> > At 1:01 AM + 2/20/04, ljb wrote:
> > >I would like to request that no changes be made to the libpgtcl
> > >chapter in the PostgreSQL reference manual, at least for the near term,
> > >beyond file revision 1.40 in CVS. Otherwise, I can't promise any
> > > changes you make will end up in my version of the manual, in the event
> > > that the unbundling effort is successful. Is this OK?
> >
> > I'm not contributing, so it's not an issue for me.
> >
> > However isn't the whole point of CVS to make re-merging changes like this
> > easy?
>
> Yes, in normal cases CVS would handle this, but the goal is to unbundle
> the Pgtcl interface and its manual from the core PostgreSQL product. This
> means there will be no more Pgtcl chapter in the PostgreSQL manual - just
> like there is no longer a chapter on the Perl interface. I've made so many
> changes to my version of this material that it is unlikely either could
> be merged into the other.
>
> My new Pgtcl version and its manual have now been released at:
>http://gborg.postgresql.org/project/pgtclng/
> There is an unpacked version of the manual for viewing on my own site:
>http://lbayuk.home.mindspring.com/pgtcldocs/
> but this is temporary, and I would like to find a more permanent place
> for it. There doesn't seem to be a way to put a docbook-generated
> manual on gborg.postgresql.org. I wonder if they would allow it on
> techdocs.postgresql.org.
I'd prefer to have the documentation live closer to the project than to have
it up on techdocs, though techdocs is probably better than someone personal
home page.
Chris, is there some way to accomplish this with gborg?
Josh, is this something that Gforge would give us?
Anyone know what the guys working on the perl interface have done?
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [DOCS] Pgtcl manual online / was: Request temporary freeze of libpgtcl...
[EMAIL PROTECTED] wrote: >... > > I'd prefer to have the documentation live closer to the project than to have > it up on techdocs, though techdocs is probably better than someone personal > home page. > > Chris, is there some way to accomplish this with gborg? > > Josh, is this something that Gforge would give us? > > Anyone know what the guys working on the perl interface have done? My mistake. I see that the Perl interface documentation was never part of the PostgreSQL Programmer's Manual. The Perl interface documentation lives inside the Pg.pm file and ends up installed and readable with perldoc. Bad example. I think there was a request on Gborg about project documentation, and the answer was to use the "genpage" feature. That's OK for a few pages with little cross-referencing, but I don't think it is practical for DocBook-generated manuals. Perhaps it isn't that important to have an unpacked version of the manual readable on the web. But for this first release, I just wanted to make it easier for people to look at, especially those who might be asking: are we unbundled yet? ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
