Greetings, Bruce!
At 18.10.2001, 02:34, you wrote:
>> Isn't it much worse to not follow PostgreSQL behavior than to not follow
>> MySQL behavior?
BM> Another idea: because our historical Limit #,# differs from MySQL, one
BM> idea is to disable LIMIT #,# completely and instead print an error
BM
Greetings, pgsql-general!
While researching material for a certain upcoming article, I found
out that online docs still claim "2001-??-??" as a release date
for PostgreSQL 7.1
--
Yours, Alexey V. Borzov, Webmaster of RDW.ru
---(end of broadcast)---
Greetings, Peter!
At 29.08.2001, 23:32, you wrote:
>> But I do think that
>> the statements in
>> http://www.mysql.com/doc/M/y/MySQL-PostgreSQL_features.html
>> should NOT go unanswered.
PE> Okay, I answered them:
PE> http://webmail.postgresql.org/~petere/comparison.html
Looks good, but i
Greetings, Tom!
At 29.03.2001, 12:52, you wrote:
TL> Alexey Borzov <[EMAIL PROTECTED]> writes:
>> The development docs state that one can use SET SEED to seed the
>> random number generator
TL> Where? I see no such claim.
Right here:
http://www.postgresql.org/devel-
Greetings, Joseph!
At 07.02.2001, 13:13, you wrote:
JS> I noticed that people are ignoring the time created part of my
JS> proposal. How can a read only field be implemented? A trigger that
JS> causes and error if that field is updated?
Well, why not just do something like
new.time_created_fiel
Greetings, Culley!
At 06.02.2001, 13:11, you wrote:
CH> Any suggestions on how to select a random record from
CH> any given table?
SELECT * FROM any_given_table ORDER BY random() LIMIT 1;
--
Yours, Alexey V. Borzov, Webmaster of RDW
Well, thanks to everybody who helped!
It was indeed the problem with opening files - the limit was set
to 1024 with more than 100 possible backends...
Well, I suppose it wouldn't hurt to change the error message in
the future versions of Postgres, 'cause now it is somewhat..
Greetings, Tom!
At 20.09.2000, 10:41, you wrote:
TL> "Alexey V. Borzov" <[EMAIL PROTECTED]> writes:
>> Nope, that's not the problem. I just checked and every DB has its own
>> PG_VERSION. Besides, _all_ of the databases are accessed on regular
>> basis (I'm speaking of a website), but the crashe
