Michael Glaesemann <[EMAIL PROTECTED]> writes:
> Just a quick heads-up: I'm not sure of the cause, but it looks like
> something recent change to HEAD and REL8_0_STABLE is causing check
> failures on the buildfarm machines. A brief (and thoroughly naive)
> glance at the details shows a horology
Just a quick heads-up: I'm not sure of the cause, but it looks like
something recent change to HEAD and REL8_0_STABLE is causing check
failures on the buildfarm machines. A brief (and thoroughly naive)
glance at the details shows a horology test failure.
Michael Glaesemann
grzm myrealbox com
--
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> On Sun, Apr 03, 2005 at 08:41:15PM -0700, Joshua D. Drake wrote:
> >
> > > What databases support perl or php stored procs/functions? Or python for
> > > that matter?
> >
> > None on the server side (except PostgreSQL) which makes the
> > argument all
On Sun, Apr 03, 2005 at 08:41:15PM -0700, Joshua D. Drake wrote:
> Jim C. Nasby wrote:
>
> >On Sat, Apr 02, 2005 at 07:29:02AM -0800, Joshua D. Drake wrote:
> >
> >
> >>This argument doesn't hold too much weight. Namely because there are only
> >>3-5 really popular languages out there. They are m
Jim C. Nasby wrote:
On Sat, Apr 02, 2005 at 07:29:02AM -0800, Joshua D. Drake wrote:
This argument doesn't hold too much weight. Namely because there are only
3-5 really popular languages out there. They are marketing languages.
The are languages you include because your database doesn't "sound"
Hi Teodor,
What exactly did you fix here?
Chris
Teodor Sigaev wrote:
I found several unpleasant blot in comparing functions and commit
changes to 7.4, 8.0 and head. Pls check (it need just to recompile .so
file)
Christopher Kings-Lynne wrote:
It's cached. This select should run only one time per
But half of the postgresql "functions" are in the grammar anyway -
they're not even listed.
Should we look at adding stub functions into pg_proc for \df display
somehow?
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Fri, Apr 01, 2005 at 12:08:54PM -, Greg Sabino Mullane wrote:
> Quoting Tom Lane:
> > I thought the "S" suggestion was much better than this.
> >
> > Personally I am not unhappy with the existing behavior, because (unlike
> > Greg I guess) I use \df and \do to look at system definitions all
Hi Ioannis,
> Also i'd like to answer you if postgresQL has implemented rcursive
> queries
> proposed from SQL99 standard?
>
Not yet. But there is a patch around that implement it. See
http://gppl.moonbone.ru/
> If yes, are there any restrictions of the model on your
> implementation?
>
The pat
On Sat, Apr 02, 2005 at 07:29:02AM -0800, Joshua D. Drake wrote:
> This argument doesn't hold too much weight. Namely because there are only
> 3-5 really popular languages out there. They are marketing languages.
> The are languages you include because your database doesn't "sound"
> complete with
Ioannis Theoharis <[EMAIL PROTECTED]> writes:
> My question is whether the way, in wich postgresql do this task, is a
> transitive closure on table 'pg_inherits' or there is a better approach
> implemented (like numbering scheme techniques etc.) ?
It's a transitive closure, and not a very bright o
Also i'd like to answer you if postgresQL has implemented rcursive queries
proposed from SQL99 standard?
If yes, are there any restrictions of the model on your implementation?
---(end of broadcast)---
TIP 2: you can get off all lists at once wit
Hi,
in case one use 'inherits' relationship to create a hierarchy of
tables, table 'pg_inherits' stores for each table the information of which
is its parent table.
During the evaluation of a query like
select * from Root;
where Root is the 'root' table of our hierarchy, postgreSQL needs to
fi
Marc G. Fournier wrote:
On Sat, 2 Apr 2005, Dave Cramer wrote:
pl-j ( the other java procedural language ) is definately interested
in being in core.
So your objectives has changed then? As I recall it, Laszlo thought it
important to keep some level of database independence with PL/J and
didn't
14 matches
Mail list logo
