Richard Huxton ([EMAIL PROTECTED]) reports a bug with a severity of 4
The lower the number the more severe it is.
Short Description
No error checking on bug submission form?
Long Description
Just posted a bug about rules, and didn't select a severity - gave an error message
"Unable to insert...
Richard Huxton ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Mis-firing of rules with a WHERE condition
Long Description
Jens Hartwig posted a question to pgsql-sql today (2001-03-06) regarding rules with
where conditions. I
Marcin Wolinski <[EMAIL PROTECTED]> writes:
> After this the 'w' class contains 116170 rows. For each value of wfid
> there are no more than 7584 different values of wnr (with median of 1
> value per wfid and only in about 1000 cases 10 values or more).
The problem here is the huge differential
Hello
This maybe a little pedantic but...
There is a slight bug in that when a user su's (with 'su' not 'su -' that
works fine) to another user the default database name changes to that
user but the one given under 'pgsql --help' does not
for example
neil-neil [~]> su
Password:
[neil@neil ne
Dear Sirs,
[This is in a way a reiteration of Marcin Zukowski's report of 19 Jan 2001
http://pgsql.service.net.pl/mhonarc/pgsql-bugs/2001-01/msg00110.html
which was ignored because of a somewhat unfortunate test case.]
I have created a new database and then have run this:
---
Ivan Baldo <[EMAIL PROTECTED]> writes:
> Simple SELECT query with simple REGEXP comparison with simple
> ORDER
> and WITHOUT JOINS CRASHES BACKEND (seems to die in an infinite loop that
> consumes CPU and uses the hard disk).
Evidently it's data-specific, since I see no problem if I just
lonnie <[EMAIL PROTECTED]> writes:
> The problem that we are finding is that PostgreSQL 7.0.3 does not seem
> to be downward compatible with previous releases of PostgreSQL. What I
> mean to say is that we have been looking at some database web
> applications such as "www-sql" and "MetaHTML" to ha
Philip Warner <[EMAIL PROTECTED]> writes:
>> If someone goes there and fixes the code, maybe the code could be optimized
>> not to put any COPY at all for a table if it is empty?
> Maybe for 7.2.
A copy supplying no data isn't going to take a significant amount of
time. I don't think this is w
Severity: Devastating
Short description:
Simple SELECT query with simple REGEXP comparison with simple
ORDER
and WITHOUT JOINS CRASHES BACKEND (seems to die in an infinite loop that
consumes CPU and uses the hard disk).
Long description:
The query:
SELECT t.* FROM t
There is no bug. You want case-insensitive pattern matching, which is
not what your call to "tolower()" accomplishes.
The query
SELECT company from user_tbl where company like lower('%SEaN%');
will find all strings which contain "sean" (note case!). It will not
match strings containing "Sean"
Hello,
My name is Lonnie Cumberland and I have recently started to migrate our
project over to PostgreSQL 7.0.3 as I really like some of the
extendability features that I see in you product.
We are working on an Internet project demo that will be shown to various
people to get our new company of
Sean Kelly ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
"select ... where field like lower('%text%')" fails
Long Description
I am trying to search a varchar(x) field with a query like "select ... where field
like lower('%so
Sean Kelly ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
"select ... where field like lower('%text%')" fails
Long Description
I am trying to search a varchar(x) field with a query like "select ... where field
like lower('%so
Hi all,
There's a spelling mistake on the users-lounge part of the PostgreSQL
website...
"pgsql-bugs If you find bug, fill "
should be :
"pgsql-bugs If you find a bug, fill "
Yes, it's small. But's it's kind of funny when you think about it. :-)
+ Justin
---(en
14 matches
Mail list logo
