Still am. ;-)
--On tisdag, december 31, 2002 10.01.34 +0800 Christopher Kings-Lynne
<[EMAIL PROTECTED]> wrote:
On Mon, 30 Dec 2002, Christopher Kings-Lynne wrote:
> ps. Why is Postgres 7.3 still in ports/databases/postgresql-devel ??
I forgot one other possible answer: perhaps the port maintai
Tara Piorkowski <[EMAIL PROTECTED]> writes:
> Regardless, my thinking had been that I was looking at an INT with a
> DEFAULT set, in which case I think this would be a bonified bug, thus my
> report.
Right --- but *if you'd declared it that way*, the system would have
reacted in the way you were
> On Mon, 30 Dec 2002, Christopher Kings-Lynne wrote:
>
> > ps. Why is Postgres 7.3 still in ports/databases/postgresql-devel ??
>
> I forgot one other possible answer: perhaps the port maintainer is taking
> a well deserved holiday?
Last time I checked, Palle _was_ the port maintainer :)
Chris
Tom Lane wrote:
Tara Piorkowski <[EMAIL PROTECTED]> writes:
junk=> create table testing
junk-> (testing_id serial not null primary key);
NOTICE: CREATE TABLE will create implicit sequence
'testing_testing_id_seq' for SERIAL column 'testing.testing_id'
NOTICE: CREATE TABLE / PRIMARY KEY will cr
Tara Piorkowski <[EMAIL PROTECTED]> writes:
> junk=> create table testing
> junk-> (testing_id serial not null primary key);
> NOTICE: CREATE TABLE will create implicit sequence
> 'testing_testing_id_seq' for SERIAL column 'testing.testing_id'
> NOTICE: CREATE TABLE / PRIMARY KEY will create imp
Christopher Kings-Lynne said:
> There have been HEAPS of security fixes between 7.2 and 7.3.
That's only the case if your definition of a "security fix" is pretty fast
and loose -- as yours seems to be.
> Depending
> on your definition of security. eg. Going 'select cash_out(2);' on any
> 7.2 se
On Sun, 29 Dec 2002 16:39:37 -0800, Kevin Brown <[EMAIL PROTECTED]>
wrote:
>> > Okay. But then doesn't it make sense for FETCH to fetch the contents
>> > of the row (and subsequent requested rows) that the cursor is
>> > currently on *then* move, and not the other way around?
>This model is extre
I've found a situation that doesn't look correct to me in 7.3.1 (and
presumably 7.3 as well). If I alter a column so that it no longer uses a
sequence for default values and then try to drop the aforementioned
sequence, the dependency checking code does not allow me to drop the
sequence on the
On Mon, 30 Dec 2002, Palle Girgensohn wrote:
> --On måndag, december 30, 2002 06.35.22 -0500 Dan Langille
> <[EMAIL PROTECTED]> wrote:
>
> > On Mon, 30 Dec 2002, Christopher Kings-Lynne wrote:
> >
> >> ps. Why is Postgres 7.3 still in ports/databases/postgresql-devel ??
> >
> > I forgot one other
--On måndag, december 30, 2002 06.35.22 -0500 Dan Langille
<[EMAIL PROTECTED]> wrote:
On Mon, 30 Dec 2002, Christopher Kings-Lynne wrote:
ps. Why is Postgres 7.3 still in ports/databases/postgresql-devel ??
I forgot one other possible answer: perhaps the port maintainer is taking
a well deser
On Mon, 30 Dec 2002, Christopher Kings-Lynne wrote:
> ps. Why is Postgres 7.3 still in ports/databases/postgresql-devel ??
I forgot one other possible answer: perhaps the port maintainer is taking
a well deserved holiday?
---(end of broadcast)---
On Mon, 30 Dec 2002, Christopher Kings-Lynne wrote:
> Since going from 7.2 to 7.3 is a significant upgrade, the FreeBSD guys would
> probablyu be right tho to refuse such a major upgrade... Still, it's a pity
> though. Postgres 7.3 has been tested and works fine on FreeBSD 5.
FreeBSD uses somet
On Mon, 30 Dec 2002, Palle Girgensohn wrote:
> One of the reasons I ask is, if it is a good reason, like say "security",
> maybe I can persuade the FreeBSD port responsible guys to bring the port
> into the upcoming FreeBSD 5.0 release. The port freeze was introduced just
> before pg-7.3 was relea
13 matches
Mail list logo
