Fwd: Re: SCHEMAS and procedures,...
- From: Vivien Malerba <malerba linuxbox com>
- To: gnome-db-list gnome org
- Subject: Fwd: Re: SCHEMAS and procedures,...
- Date: Tue, 22 Feb 2000 19:30:52 +0100
---------- Forwarded Message ----------
Subject: Re: SCHEMAS and procedures,...
Date: Tue, 22 Feb 2000 19:21:56 +0100
From: Vivien Malerba <malerba@linuxbox.com>
On mar, 22 fév 2000, Stephan Heinze wrote:
> On Tue, 22 Feb 2000 19:05:47 Vivien Malerba wrote:
> > Under Postgres, each object has a unique OID (object id), so the procs
> have
> > each their id. But how can the client know that oid since it is not
> > returned by
> > the SCHEMA_PROCS schema, or we introduce another colun in SCHEMA_PROCS
> > which
> > gives that OID, or other under other RDBMS (which would be the cleanest
> way
> > to
> > deal with multiple functions with the same name, along with an optionnal
> > constraint to specify this id)?
> >
> > What do you think?
>
> fine - and let the provider say, if he provides this
> object-identification
> or not via supports() - > the client has to know, if he has to constrain
>
> by name or if he can use the oid.
>
I propose we add a FEATURE_PROC_OBJID which returns TRUE if the client must
use the object id constraint (only, no OBJECT_NAME constraint) and FALSE if
instead he has to use the OBJECT_NAME constraint.
Also, for the SCHEMA_PROCS, we can add another column to the return (just after
the proc name) with the object id (or empty if not supported).
> PS: i hope that i can implement that stuff next week. i've read
> something
> like _release this week_?
>
Rodrigo would like to make a new release soon (early next week), and I proposed
to make a release of gASQL at the same time.
Regards.
Vivien
-------------------------------------------------------
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]