On Sun, 23 Jan 2005 12:09:26 -0600, Jeffrey Melloy
<[EMAIL PROTECTED]> wrote:
> Although Oracle doesn't have a search path, it is possible to make
> functions publicly available by doing "grant blah to public". After
> that they can be used without a schema identifier.
There is also
CREATE PUBLIC
cc:
pgsql-general@postgresql.org
[EMAIL PROTECTED]Subject: Re: [GENERAL] SCHEMA
compatibility with Oracle/DB2/Firebird
Chris wrote:
I know this isn't entirely postgresql specific, but it wouldn't be on
another list either so here goes...
I am writing an open source application where I would like to support
at least oracle, and possibly firebird or DB2, in addition to
postgresql which will be the default. I'm not g
> You'll probably be best off explicitly providing schema names for your common
> functions, e.g. SELECT * FROM common.mytable . Depending on your app,
> that could be better from a security point of view in PostgreSQL as well,
> if you want to prevent your users from sneakily replacing the common
On Sat, 22 Jan 2005 11:25:39 -0800, Chris <[EMAIL PROTECTED]> wrote:
> I know this isn't entirely postgresql specific, but it wouldn't be on
> another list either so here goes...
>
> I am writing an open source application where I would like to support
> at least oracle, and possibly firebird or D
>
> AFAIK the idea of a schema search path is specific to PG. I'm not sure
> how you will handle your "public" functions in other DBMSes.
>
>regards, tom lane
>
I'll probably have to go research this for each database. I have no
plans on immediately supporting other da
Chris <[EMAIL PROTECTED]> writes:
> ... My question is how easily would this work with other databases? I
> know Oracle supports schema's, but I dont' know about the others. I
> also don't know if other databases have the concept of a search path,
> but I would think that they do.
AFAIK the idea
I know this isn't entirely postgresql specific, but it wouldn't be on
another list either so here goes...
I am writing an open source application where I would like to support
at least oracle, and possibly firebird or DB2, in addition to
postgresql which will be the default. I'm not going to try
