Andreas Pflug wrote:
But PostgreSQL may be better than Oracle, don't you think? In the named
document,
snip
MSSQL2000 still doesn't have row level triggers, and I doubt that 2003 has.
Right, so as you've pointed out, Postgres trigger implementation is at
least in some ways more flexible than
Bruce Momjian [EMAIL PROTECTED] writes:
On a philosophical note, I usually don't add core folks to release items
_with_ other folks because we want to encourage non-core contributors,
and because there is already the assumption that core is involved in
many patches.
I agree with this. For
Oleg Bartunov wrote:
Bruce, you forgot new contrib/tsearch2 module - full text extension (Oleg,Teodor)
Sorry, added:
New tsearch2 full-text search module (Oleg)
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
Why is this not together with the mention that dollar signs are *not* allowed
anymore in operator names?
They are in different places because one relates to operator names
(Object Manipulation section) while the other relates to queries
--On Tuesday, August 05, 2003 11:29:50 -0400 Tom Lane [EMAIL PROTECTED]
wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
How is this?
Prevent timestamp from supressing ':00' seconds display
I think that was type interval, not timestamp.
Yeah, it is. (my bad, I think).
LER
regards,
No, the one where we always print hh:mm:ss for an interval, even if seconds
is zero.
--On Tuesday, August 05, 2003 01:03:57 -0400 Bruce Momjian
[EMAIL PROTECTED] wrote:
I don't know about that item. There is a menion of allowing 60 seconds
--- is that it?
I don't know about that item. There is a menion of allowing 60 seconds
--- is that it?
---
Larry Rosenman wrote:
What about the interval change in ISO datestyle for zero seconds?
LER
--On Sunday, August 03, 2003
Bruce Momjian wrote:
How are statement level triggers supposed to work? Are they just
triggers deferred until the end of the statement? You mentioned access
to the affected rows, but I don't understand how that is supposed to
happen.
I'm not sure this is a fair assessment of statement level
Done, now:
Allow thread-safe libpq with --enable-thread-safety (Lee
Kindness, Philip Yarra)
---
Lee Kindness wrote:
Bruce, I know it's a bit picky but both below should be along the
lines of Allow
How are statement level triggers supposed to work? Are they just
triggers deferred until the end of the statement? You mentioned access
to the affected rows, but I don't understand how that is supposed to
happen.
---
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Here are the changes for 7.4. I am looking for any improvements. This
will be adjusted as we move through beta.
Some notes on specific items:
Update /tmp socket files regularly to avoid their removal (Tom)
More specifically,
Bruce Momjian wrote:
How are statement level triggers supposed to work? Are they just
triggers deferred until the end of the statement? You mentioned access
to the affected rows, but I don't understand how that is supposed to
happen.
Statement level isn't about deferring or grouping the
Bruce, I know it's a bit picky but both below should be along the
lines of Allow thread-safe library since they are not threaded per
se.
L.
Bruce Momjian writes:
Libpq
Allow threaded with --enable-thread-safety (Lee Kindness, Bruce)
Miscellaneous Interfaces
Allow threaded ecpg with
Done.
---
Oleg Bartunov wrote:
On Tue, 5 Aug 2003, Bruce Momjian wrote:
Oleg Bartunov wrote:
Bruce, you forgot new contrib/tsearch2 module - full text extension (Oleg,Teodor)
Sorry, added:
New tsearch2
Neil Conway wrote:
On Mon, Aug 04, 2003 at 10:47:36AM +0200, Andreas Pflug wrote:
AFAICS the current implementation still doesn't have a way to access the
affected rowset, so it'a pretty much like a SELECT without a WHERE.
Yeah, unfortunately I didn't get a chance to implement this
I'm not sure this is a fair assessment of statement level triggers.
Yes, in MSSQL you can access the rows involved in the statement, but
in Oracle you cannot (emphasis added):
Accessing Column Values in Row Triggers
Within a trigger body of a *row trigger*, the PL/SQL code and SQL
statements
Bruce Momjian [EMAIL PROTECTED] writes:
Here are the changes for 7.4. I am looking for any improvements. This
will be adjusted as we move through beta.
Some notes on specific items:
Update /tmp socket files regularly to avoid their removal (Tom)
More specifically, update the file mod
Thinking hard about wording...
Add partially implemented FOR EACH STATEMENT statement-level triggers (Neil Conway)
which doesn't look nice but expresses what's implemented. Taken from the
CREATE TRIGGER FOR EACH STATEMENT documentation, a user would think he
could do the same stuff as on lets
OK, I moved them both to the object section, next to each other.
---
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
Why is this not together with the mention that dollar signs are *not* allowed
--On Tuesday, August 05, 2003 10:36:32 -0400 Bruce Momjian
[EMAIL PROTECTED] wrote:
Oh, yes. Let me add that. I didn't realize that was a change of enough
significance.
How is this?
Prevent timestamp from supressing ':00' seconds display
Yes, considering that it's a format change and Tom
On Tue, 5 Aug 2003, Bruce Momjian wrote:
Oleg Bartunov wrote:
Bruce, you forgot new contrib/tsearch2 module - full text extension (Oleg,Teodor)
Sorry, added:
New tsearch2 full-text search module (Oleg)
Bruce, I wrote (Oleg,Teodor)
Regards,
Oleg
Joe Conway wrote:
Bruce Momjian wrote:
Here are the changes for 7.4. I am looking for any improvements. This
will be adjusted as we move through beta.
Almost anything with my name on it (but certainly all the array and
polymorphic function stuff) could have Tom's too, since he
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
On a philosophical note, I usually don't add core folks to release items
_with_ other folks because we want to encourage non-core contributors,
and because there is already the assumption that core is involved in
many patches.
I
Do you have suggested wording?
---
Andreas Pflug wrote:
Bruce Momjian wrote:
Here are the changes for 7.4. I am looking for any improvements. This
will be adjusted as we move through beta.
Bruce Momjian [EMAIL PROTECTED] writes:
How is this?
Prevent timestamp from supressing ':00' seconds display
I think that was type interval, not timestamp.
regards, tom lane
---(end of broadcast)---
TIP 3: if
Updated. Thanks.
---
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
How is this?
Prevent timestamp from supressing ':00' seconds display
I think that was type interval, not timestamp.
Joe Conway wrote:
Andreas Pflug wrote:
But PostgreSQL may be better than Oracle, don't you think? In the
named document,
snip
MSSQL2000 still doesn't have row level triggers, and I doubt that
2003 has.
Right, so as you've pointed out, Postgres trigger implementation is at
least in some
Oh, yes. Let me add that. I didn't realize that was a change of enough
significance.
How is this?
Prevent timestamp from supressing ':00' seconds display
---
Larry Rosenman wrote:
No, the one where we always
On Mon, Aug 04, 2003 at 10:47:36AM +0200, Andreas Pflug wrote:
AFAICS the current implementation still doesn't have a way to access the
affected rowset, so it'a pretty much like a SELECT without a WHERE.
Yeah, unfortunately I didn't get a chance to implement this functionality
during the 7.4
PROTECTED]
To: Bruce Momjian [EMAIL PROTECTED]
Cc: PostgreSQL-development [EMAIL PROTECTED]
Sent: Monday, August 04, 2003 1:28 PM
Subject: Re: [HACKERS] Release changes
Bruce, you forgot new contrib/tsearch2 module - full text extension
(Oleg,Teodor)
Regards,
Oleg
Bruce Momjian wrote:
Here are the changes for 7.4. I am looking for any improvements. This
will be adjusted as we move through beta.
---
Add FOR EACH STATEMENT statement-level triggers (Neil Conway)
AFAICS the current
Oleg Bartunov [EMAIL PROTECTED] writes:
On Mon, 4 Aug 2003, Christopher Kings-Lynne wrote:
Oleg - have you followed the latest discussion on why tsearch2 isn't
compilable on FreeBSD?
Nop, Teodor's development machine is FreeBSD and he has no problem :)
I think the problem may only occur when
Here are the changes for 7.4. I am looking for any improvements. This
will be adjusted as we move through beta.
I need to work on the other sections of a major release, like a
compatibility section.
---
No, not for 7.4.
---
snpe wrote:
On Sunday 03 August 2003 11:30 pm, Bruce Momjian wrote:
Here are the changes for 7.4. I am looking for any improvements. This
will be adjusted as we move through beta.
I need to
Bruce Momjian wrote:
Here are the changes for 7.4. I am looking for any improvements. This
will be adjusted as we move through beta.
Almost anything with my name on it (but certainly all the array and
polymorphic function stuff) could have Tom's too, since he reviewed,
polished, and applied
What about the interval change in ISO datestyle for zero seconds?
LER
--On Sunday, August 03, 2003 19:30:26 -0400 Bruce Momjian
[EMAIL PROTECTED] wrote:
Here are the changes for 7.4. I am looking for any improvements. This
will be adjusted as we move through beta.
I need to work on the other
Bruce, you forgot new contrib/tsearch2 module - full text extension (Oleg,Teodor)
Regards,
Oleg
_
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
: [HACKERS] Release changes
Bruce, you forgot new contrib/tsearch2 module - full text extension
(Oleg,Teodor)
Regards,
Oleg
_
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow
38 matches
Mail list logo
