Gavin Sherry wrote: > > A few examples on the command references pages to show how it can be > > useful are probably OK, but the big picture shoulbd be developed in > > chapter 7 or so. > > What do we want to do about documenting: > > regression=# values(1); > column1 > --------- > 1 > (1 row) > > It seems to me that if this isn't in the command reference we'll see an > email every few months say 'is this an undocumented feature?'. We can > cover it easily in Part II, 7.2 but people wont look there. Then again, it > just doesn't seem right to put it in the command reference as a 'top > level' command.
How many people are going to think of doing a VALUES(1)? Isn't it just like SELECT 1? We can try making VALUES a non-toplevel command, and if people get confused, we can promote in the documenation. I think starting it at top-level is perhaps confusing. -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
