I've committed some changes which implement a few new things.

 From the CVS log:

Implement nested block comments in the backend and in psql.
 Include updates for the comment.sql regression test.
Implement SET SESSION CHARACTERISTICS and SET DefaultXactIsoLevel.
Implement SET SESSION CHARACTERISTICS TRANSACTION COMMIT
 and SET AutoCommit in the parser only.
 Need to add code to actually do something.
Implement WITHOUT TIME ZONE type qualifier.
Define SCHEMA keyword, along with stubbed-out grammar.
Implement "[IN|INOUT|OUT] [varname] type" function arguments
 in parser only; INOUT and OUT throws an elog(ERROR).
Add PATH as a type-specific token, since PATH is in SQL99
 to support schema resource search and resolution.

Since some of these changes involve tokens in the parser, you may need
to do a "make clean all install" to get everything sync'd. afaict this
is because we propagate a few of the gram.y token values deeper into the
backend...

                   - Thomas

Fri, 14 Jul 2000 16:14:28 +0000
Thomas Lockhart <lockhart@alumni.caltech.edu>
Just committed some changes...
On Fri, Jul 14, 2000 at 04:14:28PM +0000, Thomas Lockhart wrote:
> Define SCHEMA keyword, along with stubbed-out grammar.

I was just digging into pgaccess a little, cleaning up the 
diagramming feature I had added. In a fit of naivete, I had
called them "schema", as in the logical idea, not the 
SQL key word. Since we're going to be implementing SQL SCHEMA,
eventually, perhaps this would be a good time to rename this
feature in pgaccess. 

How does "Diagrams" sound? Anyone have a better idea? The name appears
on a tab. The other tabs are labelled:

Tables, Queries, Views, Sequences, Functions, Reports, Forms, Scripts,
Users, ????.

Keep in mind, I have been thinking about connecting the schema diagrammer
into the visual query builder, so that you can set a 'strict' mode,
where it'll only allow joins that have been defined in the schema
editor. That's why I named it schema, in the first place.  It'd be nice to
have the diagramming interact with primary key/foreign key constraints,
optionally drawing them in automatically. However, all it does right
now is draw tables and let you draw links between them, by dragging and
dropping fieldnames.

Ross
-- 
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu> 
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St.,  Houston, TX 77005



Fri, 14 Jul 2000 14:43:02 -0500
"Ross J. Reedstrom" <reedstrm@rice.edu>
PgAccess diagrams (was: Re: Just committed some changes...)
> How does "Diagrams" sound? Anyone have a better idea? The name appears
> on a tab. The other tabs are labelled:

OK with me...

                - Thomas

Sat, 15 Jul 2000 01:46:07 +0000
Thomas Lockhart <lockhart@alumni.caltech.edu>
Re: PgAccess diagrams (was: Re: Just committed some
 changes...)
"Ross J. Reedstrom" wrote:
> 
> How does "Diagrams" sound? Anyone have a better idea? The name appears
> on a tab. The other tabs are labelled:

Sounds fine to me.

Anyway, you are the people speaking english all day long :-) and you
should say if it's ok

I'll apply the pathes to the next PgAccess release.

Constantin Teodorescu
Braila, ROMANIA

Sat, 15 Jul 2000 18:51:52 +0300
Constantin Teodorescu <teo@flex.ro>
Re: PgAccess diagrams (was: Re: Just committed some
 changes...)