pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
"SQL" REPLACE SYNTAX
15+ messages / 7 participants
[nested] [flat]

* "SQL" REPLACE SYNTAX
@ 2002-01-23 01:44  Christopher Kings-Lynne <chriskl@familyhealth.com.au>
  0 siblings, 3 replies; 15+ messages in thread

From: Christopher Kings-Lynne @ 2002-01-23 01:44 UTC (permalink / raw)
  To: Francisco Reyes <lists@natserv.com>; +Cc: Manuel Lemos <mlemos@acm.org>; pgsql-php

> We can discuss names, till the cows come home, but basically Manuel
> described what he meant. The "replace" functionality is one of the few
> things I liked of MySQL when I researched which dB to go with. The fact
> that this layer can abstract the functionality is a great point in my
> opinion.

Here's an idea:  look at their code to see what kind of SQL jiggery pokery
they needed to implement it and then implement it ourselves...

BTW, from my estimates you'd need at least 4 - 6 sql queries to simulate the
REPLACE syntax for Postgres, so why on earth would you use it?

Chris




^ permalink  raw  reply  [nested|flat] 15+ messages in thread

* Re: "SQL" REPLACE SYNTAX
@ 2002-01-23 03:52  Francisco Reyes <lists@natserv.com>
  parent: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
  2 siblings, 1 reply; 15+ messages in thread

From: Francisco Reyes @ 2002-01-23 03:52 UTC (permalink / raw)
  To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>; +Cc: Manuel Lemos <mlemos@acm.org>; pgsql-php

On Wed, 23 Jan 2002, Christopher Kings-Lynne wrote:

> Here's an idea:  look at their code to see what kind of SQL jiggery pokery
> they needed to implement it and then implement it ourselves...

I wish PostgreSQL got this functionality.
>
> BTW, from my estimates you'd need at least 4 - 6 sql queries to simulate the
> REPLACE syntax for Postgres, so why on earth would you use it?
> Chris

Why so many? It is simple enough to attempt a delete and then do an
insert.




^ permalink  raw  reply  [nested|flat] 15+ messages in thread

* Re: "SQL" REPLACE SYNTAX
@ 2002-01-23 03:56  Christopher Kings-Lynne <chriskl@familyhealth.com.au>
  parent: Francisco Reyes <lists@natserv.com>
  0 siblings, 1 reply; 15+ messages in thread

From: Christopher Kings-Lynne @ 2002-01-23 03:56 UTC (permalink / raw)
  To: Francisco Reyes <lists@natserv.com>; +Cc: Manuel Lemos <mlemos@acm.org>; pgsql-php

> Why so many? It is simple enough to attempt a delete and then do an
> insert.

DELETE WHERE what?  Alternatively you can attempt and update then do an
insert - question is UPDATE WHERE what?

If the insert fails you need to select from the postgres system catalogs to
find the primary key on the table (if there is one).  Next, you need to find
the fields that that primary key is defined over.  Next, you need to parse
the insert statement and find the fields being inserted that match the
primary key.  Lastly you need to modify the insert statment to an update
statment, take out the values that are part of the primary key and make them
part of the where clause of the update or delete statement.

Chris




^ permalink  raw  reply  [nested|flat] 15+ messages in thread

* Re: "SQL" REPLACE SYNTAX
@ 2002-01-23 04:39  Manuel Lemos <mlemos@acm.org>
  parent: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
  2 siblings, 1 reply; 15+ messages in thread

From: Manuel Lemos @ 2002-01-23 04:39 UTC (permalink / raw)
  To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>; +Cc: Francisco Reyes <lists@natserv.com>; pgsql-php

Hello,

Christopher Kings-Lynne wrote:
> 
> > We can discuss names, till the cows come home, but basically Manuel
> > described what he meant. The "replace" functionality is one of the few
> > things I liked of MySQL when I researched which dB to go with. The fact
> > that this layer can abstract the functionality is a great point in my
> > opinion.
> 
> Here's an idea:  look at their code to see what kind of SQL jiggery pokery
> they needed to implement it and then implement it ourselves...
> 
> BTW, from my estimates you'd need at least 4 - 6 sql queries to simulate the
> REPLACE syntax for Postgres, so why on earth would you use it?

Actually only two: a SELECT and a depending on that, a INSERT or an
UPDATE. You may want to try to look at Metabase implementation to see
how it works.

Regards,
Manuel Lemos



^ permalink  raw  reply  [nested|flat] 15+ messages in thread

* Re: "SQL" REPLACE SYNTAX
@ 2002-01-23 05:21  Christopher Kings-Lynne <chriskl@familyhealth.com.au>
  parent: Manuel Lemos <mlemos@acm.org>
  0 siblings, 1 reply; 15+ messages in thread

From: Christopher Kings-Lynne @ 2002-01-23 05:21 UTC (permalink / raw)
  To: Manuel Lemos <mlemos@acm.org>; +Cc: Francisco Reyes <lists@natserv.com>; pgsql-php

> Actually only two: a SELECT and a depending on that, a INSERT or an
> UPDATE. You may want to try to look at Metabase implementation to see
> how it works.

Read my previous post.  How does MetaBase know which fields are the primary
key!?!?!?!?

Chris




^ permalink  raw  reply  [nested|flat] 15+ messages in thread

* Re: "SQL" REPLACE SYNTAX
@ 2002-01-23 05:26  Manuel Lemos <mlemos@acm.org>
  parent: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
  0 siblings, 1 reply; 15+ messages in thread

From: Manuel Lemos @ 2002-01-23 05:26 UTC (permalink / raw)
  To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>; +Cc: Francisco Reyes <lists@natserv.com>; pgsql-php

Hello,

Christopher Kings-Lynne wrote:
> 
> > Actually only two: a SELECT and a depending on that, a INSERT or an
> > UPDATE. You may want to try to look at Metabase implementation to see
> > how it works.
> 
> Read my previous post.  How does MetaBase know which fields are the primary
> key!?!?!?!?

Look at Metabase implementation. Metabase comes with a driver
conformance test that verifies if features like this work properly in
all supported databases. Don't you think that I would release a version
of Metabase that would not pass that test if all databases?

The application needs to hint it as it is something that does not change
at runtime, so there is no penalty of figuring that by querying the
database server and some database do not provide a way to tell you which
fields are the primary key.

Regards,
Manuel Lemos



^ permalink  raw  reply  [nested|flat] 15+ messages in thread

* Re: "SQL" REPLACE SYNTAX
@ 2002-01-23 05:41  Christopher Kings-Lynne <chriskl@familyhealth.com.au>
  parent: Manuel Lemos <mlemos@acm.org>
  0 siblings, 1 reply; 15+ messages in thread

From: Christopher Kings-Lynne @ 2002-01-23 05:41 UTC (permalink / raw)
  To: Manuel Lemos <mlemos@acm.org>; +Cc: Francisco Reyes <lists@natserv.com>; pgsql-php

> Look at Metabase implementation. Metabase comes with a driver
> conformance test that verifies if features like this work properly in
> all supported databases. Don't you think that I would release a version
> of Metabase that would not pass that test if all databases?
>
> The application needs to hint it as it is something that does not change
> at runtime, so there is no penalty of figuring that by querying the
> database server and some database do not provide a way to tell you which
> fields are the primary key.

OK, so it's not a simulation of the MySQL syntax - MySQL requires no hints.
I've looked thru the code and yeah, basically that's what you have to do, so
long as you can get the app programmer to tell you in the code what the
primary keys are.  For a postgres implementation, it's more difficult.

BTW, there's no documentation anywhere in your code - makes it a bit
difficult to see what's going on...

Chris




^ permalink  raw  reply  [nested|flat] 15+ messages in thread

* Re: "SQL" REPLACE SYNTAX
@ 2002-01-23 05:54  Manuel Lemos <mlemos@acm.org>
  parent: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
  0 siblings, 0 replies; 15+ messages in thread

From: Manuel Lemos @ 2002-01-23 05:54 UTC (permalink / raw)
  To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>; +Cc: Francisco Reyes <lists@natserv.com>; pgsql-php

Hello,

Christopher Kings-Lynne wrote:
> 
> > Look at Metabase implementation. Metabase comes with a driver
> > conformance test that verifies if features like this work properly in
> > all supported databases. Don't you think that I would release a version
> > of Metabase that would not pass that test if all databases?
> >
> > The application needs to hint it as it is something that does not change
> > at runtime, so there is no penalty of figuring that by querying the
> > database server and some database do not provide a way to tell you which
> > fields are the primary key.
> 
> OK, so it's not a simulation of the MySQL syntax - MySQL requires no hints.

No, but the functionality is the same. MySQL ignores the hints because
SQL REPLACE works as intended without the hints.



> I've looked thru the code and yeah, basically that's what you have to do, so
> long as you can get the app programmer to tell you in the code what the
> primary keys are.  For a postgres implementation, it's more difficult.

It is required. If the programmer does not tell which fields are the
keys, the function will fail with an error stating that.


 
> BTW, there's no documentation anywhere in your code - makes it a bit
> difficult to see what's going on...

Erm.... there is 248K HTML document that details all about that function
the whole Metabase API. :-)

Regards,
Manuel Lemos



^ permalink  raw  reply  [nested|flat] 15+ messages in thread

* Re: "SQL" REPLACE SYNTAX
@ 2002-01-23 10:52  Andrew McMillan <andrew@catalyst.net.nz>
  parent: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
  0 siblings, 1 reply; 15+ messages in thread

From: Andrew McMillan @ 2002-01-23 10:52 UTC (permalink / raw)
  To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>; +Cc: pgsql-php; Manuel Lemos <mlemos@acm.org>

On Wed, 2002-01-23 at 16:56, Christopher Kings-Lynne wrote:
> > Why so many? It is simple enough to attempt a delete and then do an
> > insert.
> 
> DELETE WHERE what?  Alternatively you can attempt and update then do an
> insert - question is UPDATE WHERE what?
> 
> If the insert fails you need to select from the postgres system catalogs to
> find the primary key on the table (if there is one).  Next, you need to find
> the fields that that primary key is defined over.  Next, you need to parse
> the insert statement and find the fields being inserted that match the
> primary key.  Lastly you need to modify the insert statment to an update
> statment, take out the values that are part of the primary key and make them
> part of the where clause of the update or delete statement.

I realise this wanders far from the SQL standard, but it's one of those
areas where the standard is awkward from an application programmer's
point of view.   I would certainly love to see some syntax of this kind
available.  If having to work out the primary key from schema queries is
too much work, then why not have a syntax that explicitly coped - after
all the whole thing is non-standard, so we don't have to follow MySQL's
lead on it:

INSERT OR REPLACE <table> ( <field list> )
         VALUES( <value list> ) WHERE <condition>

would be just fine by me.

There are many places in my programs where I want to do this sort of
INSERT OR REPLACE functionality and the ability to do so would make my
code more maintainable, and much less prone to stupid errors.

More simply (?) I want to be able to build the fields / values for my
query and then decide at the last minute whether I was doing an INSERT
or an UPDATE.

To do this (without throwing an error) I currently do a "SELECT ...
WHERE <condition>;" and then construct my SQL appropriately.  When I add
a new column to a table (this is the real world :-) I frequently forget
to maintain one branch of the resulting code building the SQL statement.

It is this need that Manuel is catering for by implementing the
functionality in Metabase, but I expect it would be more efficient to
implement it in PostgreSQL natively.

Cheers,
					Andrew.
-- 
--------------------------------------------------------------------
Andrew @ Catalyst .Net.NZ Ltd, PO Box 11-053, Manners St, Wellington
WEB: http://catalyst.net.nz/        PHYS: Level 2, 150-154 Willis St
DDI: +64(4)916-7201    MOB: +64(21)635-694    OFFICE: +64(4)499-2267
       Are you enrolled at http://schoolreunions.co.nz/ yet?




^ permalink  raw  reply  [nested|flat] 15+ messages in thread

* Re: "SQL" REPLACE SYNTAX
@ 2002-01-23 11:15  Papp Gyozo <pgerzson@freestart.hu>
  parent: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
  2 siblings, 0 replies; 15+ messages in thread

From: Papp Gyozo @ 2002-01-23 11:15 UTC (permalink / raw)
  To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>; pgsql-php

Hi,
| 
| BTW, from my estimates you'd need at least 4 - 6 sql queries to simulate the
| REPLACE syntax for Postgres, so why on earth would you use it?
| 

I think Chris would be right. In my approach the true emulation of REPLACE 
syntax is the following:

1. BEGIN;

2. SELECT ... FOR UPDATE; 

3a.  UPDATE ...;
3b.  INSERT ...;

4. COMMIT;

I think each step is required to do a foolproof code.
Transaction (BEGIN and COMMIT) guarantees the atomicity for so called "REPLACE",
and the "FOR UPDATE" clause locks the corresponding row, if it exists.
(AFAIR, it works only in transaction, obvoiusly.)

So, it takes 4 SQL statements.

Papp Gyozo
- pgerzson@freestart.hu



^ permalink  raw  reply  [nested|flat] 15+ messages in thread

* Re: "SQL" REPLACE SYNTAX
@ 2002-01-23 11:24  Vince Vielhaber <vev@michvhf.com>
  parent: Andrew McMillan <andrew@catalyst.net.nz>
  0 siblings, 2 replies; 15+ messages in thread

From: Vince Vielhaber @ 2002-01-23 11:24 UTC (permalink / raw)
  To: Andrew McMillan <andrew@catalyst.net.nz>; +Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>; pgsql-php; Manuel Lemos <mlemos@acm.org>

On 23 Jan 2002, Andrew McMillan wrote:

> I realise this wanders far from the SQL standard, but it's one of those
> areas where the standard is awkward from an application programmer's
> point of view.   I would certainly love to see some syntax of this kind
> available.  If having to work out the primary key from schema queries is
> too much work, then why not have a syntax that explicitly coped - after
> all the whole thing is non-standard, so we don't have to follow MySQL's
> lead on it:
>
> INSERT OR REPLACE <table> ( <field list> )
>          VALUES( <value list> ) WHERE <condition>
>
> would be just fine by me.
>
> There are many places in my programs where I want to do this sort of
> INSERT OR REPLACE functionality and the ability to do so would make my
> code more maintainable, and much less prone to stupid errors.
>
> More simply (?) I want to be able to build the fields / values for my
> query and then decide at the last minute whether I was doing an INSERT
> or an UPDATE.
>
> To do this (without throwing an error) I currently do a "SELECT ...
> WHERE <condition>;" and then construct my SQL appropriately.  When I add
> a new column to a table (this is the real world :-) I frequently forget
> to maintain one branch of the resulting code building the SQL statement.
>
> It is this need that Manuel is catering for by implementing the
> functionality in Metabase, but I expect it would be more efficient to
> implement it in PostgreSQL natively.

INSERT OR REPLACE table1(a,b,c) VALUES(1,2,3) WHERE a=3 and b=4 and c=5;

On the surface it looks ok.  But..  What happens if you have a table
that isn't just a,b,c there are actually a,b,c,d,e,f and there are more
than one tuple with a=3 and b=4 and c=5?  Do you replace them all or
throw an error?  Isn't this what Chris was eluding to?

BTW, INSERT OR UPDATE seems more appropriate since you'd be doing an
UPDATE if the row already exists.  I think that's also what Oracle uses.

Vince.
-- 
==========================================================================
Vince Vielhaber -- KA8CSH    email: vev@michvhf.com    http://www.pop4.net
         56K Nationwide Dialup from $16.00/mo at Pop4 Networking
        Online Campground Directory    http://www.camping-usa.com
       Online Giftshop Superstore    http://www.cloudninegifts.com
==========================================================================






^ permalink  raw  reply  [nested|flat] 15+ messages in thread

* Re: "SQL" REPLACE SYNTAX
@ 2002-01-23 11:41  Andrew McMillan <andrew@catalyst.net.nz>
  parent: Vince Vielhaber <vev@michvhf.com>
  1 sibling, 1 reply; 15+ messages in thread

From: Andrew McMillan @ 2002-01-23 11:41 UTC (permalink / raw)
  To: Vince Vielhaber <vev@michvhf.com>; +Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>; pgsql-php; Manuel Lemos <mlemos@acm.org>

On Thu, 2002-01-24 at 00:24, Vince Vielhaber wrote:
> 
> INSERT OR REPLACE table1(a,b,c) VALUES(1,2,3) WHERE a=3 and b=4 and c=5;
> 
> On the surface it looks ok.  But..  What happens if you have a table
> that isn't just a,b,c there are actually a,b,c,d,e,f and there are more
> than one tuple with a=3 and b=4 and c=5?  Do you replace them all or
> throw an error?  Isn't this what Chris was eluding to?

OK, so the implementor would have to decide what to do if the condition
matched more than one row, but I'd be happy with _whatever_ was decided
in that regard.

To be honest, I'd even pay the six-query price that Christopher talks
about for the improved ease of maintainability of my scripts that I
would gain.  If query efficiency was a concern then I would code around
that as required, because that is usually the exception especially for
the sorts of situations where INSERT OR UPDATE syntax is useful.


> BTW, INSERT OR UPDATE seems more appropriate since you'd be doing an
> UPDATE if the row already exists.  I think that's also what Oracle uses.

You're probably right.  I do remember they use CREATE OR REPLACE for
procedures and such, but I don't use Oracle too much nowadays :-)

Cheers,
					Andrew.
-- 
--------------------------------------------------------------------
Andrew @ Catalyst .Net.NZ Ltd, PO Box 11-053, Manners St, Wellington
WEB: http://catalyst.net.nz/        PHYS: Level 2, 150-154 Willis St
DDI: +64(4)916-7201    MOB: +64(21)635-694    OFFICE: +64(4)499-2267
       Are you enrolled at http://schoolreunions.co.nz/ yet?




^ permalink  raw  reply  [nested|flat] 15+ messages in thread

* Re: "SQL" REPLACE SYNTAX
@ 2002-01-23 21:39  Josh Berkus <josh@agliodbs.com>
  parent: Andrew McMillan <andrew@catalyst.net.nz>
  0 siblings, 1 reply; 15+ messages in thread

From: Josh Berkus @ 2002-01-23 21:39 UTC (permalink / raw)
  To: Andrew McMillan <andrew@catalyst.net.nz>; Vince Vielhaber <vev@michvhf.com>; +Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>; pgsql-php; Manuel Lemos <mlemos@acm.org>

Folks,

You can propose this syntax additon on the pgsql-sql list, which exists
 to discuss these kinds of issues.  However, I will warn you that the
 core developers have already rejected the REPLACE syntax once as an
 unnecessary deviation from the SQL92 standard.

There was a long discussion following that rejection, sometime last
 summer I think, about how one could use triggers or rules to ape this
 functionality on an INSERT statement.  See the pgsql-sql list
 archives.

You can, of course, also write the ANSI committee and propose that
 REPLACE be added to SQL3.  Good luck.

-Josh Berkus

______AGLIO DATABASE SOLUTIONS___________________________
                                       Josh Berkus
  Complete information technology      josh@agliodbs.com
   and data management solutions       (415) 565-7293
  for law firms, small businesses        fax 621-2533
    and non-profit organizations.      San Francisco



^ permalink  raw  reply  [nested|flat] 15+ messages in thread

* Re: "SQL" REPLACE SYNTAX
@ 2002-01-24 00:29  Vince Vielhaber <vev@michvhf.com>
  parent: Josh Berkus <josh@agliodbs.com>
  0 siblings, 0 replies; 15+ messages in thread

From: Vince Vielhaber @ 2002-01-24 00:29 UTC (permalink / raw)
  To: Josh Berkus <josh@agliodbs.com>; +Cc: Andrew McMillan <andrew@catalyst.net.nz>; Christopher Kings-Lynne <chriskl@familyhealth.com.au>; pgsql-php; Manuel Lemos <mlemos@acm.org>

On Wed, 23 Jan 2002, Josh Berkus wrote:

> Folks,
>
> You can propose this syntax additon on the pgsql-sql list, which exists
>  to discuss these kinds of issues.  However, I will warn you that the
>  core developers have already rejected the REPLACE syntax once as an
>  unnecessary deviation from the SQL92 standard.
>
> There was a long discussion following that rejection, sometime last
>  summer I think, about how one could use triggers or rules to ape this
>  functionality on an INSERT statement.  See the pgsql-sql list
>  archives.
>
> You can, of course, also write the ANSI committee and propose that
>  REPLACE be added to SQL3.  Good luck.

Has it ever been brought up on hackers?  I remember the create or
replace stuff conversation, but that was regarding functions.  I
can't remember anything about insert or update.  Chris, maybe you
wanna bring it up there?  I'm going to be available only on a limited
basis the next couple of weeks or so or I would.

Vince.
-- 
==========================================================================
Vince Vielhaber -- KA8CSH    email: vev@michvhf.com    http://www.pop4.net
         56K Nationwide Dialup from $16.00/mo at Pop4 Networking
        Online Campground Directory    http://www.camping-usa.com
       Online Giftshop Superstore    http://www.cloudninegifts.com
==========================================================================






^ permalink  raw  reply  [nested|flat] 15+ messages in thread

* Re: "SQL" REPLACE SYNTAX
@ 2002-01-24 00:57  Manuel Lemos <mlemos@acm.org>
  parent: Vince Vielhaber <vev@michvhf.com>
  1 sibling, 0 replies; 15+ messages in thread

From: Manuel Lemos @ 2002-01-24 00:57 UTC (permalink / raw)
  To: Vince Vielhaber <vev@michvhf.com>; +Cc: Andrew McMillan <andrew@catalyst.net.nz>; Christopher Kings-Lynne <chriskl@familyhealth.com.au>; pgsql-php

Hello,

Vince Vielhaber wrote:
> 
> On 23 Jan 2002, Andrew McMillan wrote:
> 
> > I realise this wanders far from the SQL standard, but it's one of those
> > areas where the standard is awkward from an application programmer's
> > point of view.   I would certainly love to see some syntax of this kind
> > available.  If having to work out the primary key from schema queries is
> > too much work, then why not have a syntax that explicitly coped - after
> > all the whole thing is non-standard, so we don't have to follow MySQL's
> > lead on it:
> >
> > INSERT OR REPLACE <table> ( <field list> )
> >          VALUES( <value list> ) WHERE <condition>
> >
> > would be just fine by me.
> >
> > There are many places in my programs where I want to do this sort of
> > INSERT OR REPLACE functionality and the ability to do so would make my
> > code more maintainable, and much less prone to stupid errors.
> >
> > More simply (?) I want to be able to build the fields / values for my
> > query and then decide at the last minute whether I was doing an INSERT
> > or an UPDATE.
> >
> > To do this (without throwing an error) I currently do a "SELECT ...
> > WHERE <condition>;" and then construct my SQL appropriately.  When I add
> > a new column to a table (this is the real world :-) I frequently forget
> > to maintain one branch of the resulting code building the SQL statement.
> >
> > It is this need that Manuel is catering for by implementing the
> > functionality in Metabase, but I expect it would be more efficient to
> > implement it in PostgreSQL natively.
> 
> INSERT OR REPLACE table1(a,b,c) VALUES(1,2,3) WHERE a=3 and b=4 and c=5;

REPLACE only uses the primary key to figure if a row exists, so it won't
find more than one row.

 
> BTW, INSERT OR UPDATE seems more appropriate since you'd be doing an
> UPDATE if the row already exists.  I think that's also what Oracle uses.

That's what Metabase uses as default implementation, it works in
PostgreSQL, Oracle, MS SQL server, Informix, Interbase and eventually
with any ODBC data source that supports SQL and transactions.

Regards,
Manuel Lemos



^ permalink  raw  reply  [nested|flat] 15+ messages in thread


end of thread, other threads:[~2002-01-24 00:57 UTC | newest]

Thread overview: 15+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2002-01-23 01:44 "SQL" REPLACE SYNTAX Christopher Kings-Lynne <chriskl@familyhealth.com.au>
2002-01-23 03:52 ` Francisco Reyes <lists@natserv.com>
2002-01-23 03:56   ` Christopher Kings-Lynne <chriskl@familyhealth.com.au>
2002-01-23 10:52     ` Andrew McMillan <andrew@catalyst.net.nz>
2002-01-23 11:24       ` Vince Vielhaber <vev@michvhf.com>
2002-01-23 11:41         ` Andrew McMillan <andrew@catalyst.net.nz>
2002-01-23 21:39           ` Josh Berkus <josh@agliodbs.com>
2002-01-24 00:29             ` Vince Vielhaber <vev@michvhf.com>
2002-01-24 00:57         ` Manuel Lemos <mlemos@acm.org>
2002-01-23 04:39 ` Manuel Lemos <mlemos@acm.org>
2002-01-23 05:21   ` Christopher Kings-Lynne <chriskl@familyhealth.com.au>
2002-01-23 05:26     ` Manuel Lemos <mlemos@acm.org>
2002-01-23 05:41       ` Christopher Kings-Lynne <chriskl@familyhealth.com.au>
2002-01-23 05:54         ` Manuel Lemos <mlemos@acm.org>
2002-01-23 11:15 ` Papp Gyozo <pgerzson@freestart.hu>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox