Bruce Momjian wrote:
Aleksej Saushev wrote:
The following bug has been logged online:
Bug reference: 4053
Logged by: Aleksej Saushev
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3
Operating system: NetBSD, but this does no matter
Description:libpq document
Aleksej Saushev wrote:
>
> The following bug has been logged online:
>
> Bug reference: 4053
> Logged by: Aleksej Saushev
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.3
> Operating system: NetBSD, but this does no matter
> Description:libpq documentation
Peter Eisentraut wrote:
> Am Montag, 17. M?rz 2008 schrieb Mika Fischer:
> > Ideally, psql should provide an option --no-password which would cause it
> > to never promt for a password, and in case one is needed, fail as if a
> > wrong one was given.
>
> Something like ssh's BatchMode would be nic
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > BTW while reading the psql manpage I noticed this statement:
>
> >A popular application of this facility is to refer to the last
> >inserted OID in subsequent statements to build a foreign key
> >scenario.
>
<[EMAIL PROTECTED]> writes:
>> Aliases in the select list are not in scope in the having clause.
> it will be good if aliases will be in scope of 'having' clause.
Feel free to try to convince the SQL standards committee ...
regards, tom lane
--
Sent via pgsql-bugs maili
Aliases in the select list are not in scope in the having clause.
it will be good if aliases will be in scope of 'having' clause.
Because of dublicating code is cause of bugs when people foget replace code
in second place while changing code in first one =(
- Original Message -
From:
"" <[EMAIL PROTECTED]> writes:
> for query SELECT to_tsvector('surprise') it's showing result as 'surpris':1
> but when I try to search this word its returning false.
> SELECT to_tsvector('surprise') @@ to_tsquery('surpris');
This isn't a bug, because those are not the same word. If you looked
c
Would someone please respond to this bug report?
---
Matt Magoffin wrote:
>
> The following bug has been logged online:
>
> Bug reference: 4024
> Logged by: Matt Magoffin
> Email address: [EMAIL PROTECTE
The following bug has been logged online:
Bug reference: 4148
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3
Operating system: windows xp
Description:tsearch related issue
Details:
Hi,
I'm using tsearch in my application.
for query SELECT to
PostgreSQL 8.3 added a new optimization to avoid sorting in queries that
use ORDER BY ... LIMIT. This optimization does not work when the query
is issued to a parent table with several children, such as a partitioned
table.
PostgreSQL version: 8.3.1
Operating System:RedHat Enterprise Li
Am Mittwoch, 7. Mai 2008 schrieb [EMAIL PROTECTED]:
> SELECT
> MIN(COALESCE(cmp_values(parent_td.value, parent_md.value,
> parent_cmp.value),0)) as chk_parent, FROM some_table
>
> having chk_parent > 0
>
> ERROR: column "chk_parent" does not exist at character 2342
Aliases in the select list are
SELECT
MIN(COALESCE(cmp_values(parent_td.value, parent_md.value, parent_cmp.value),0))
as chk_parent,
FROM some_table
having chk_parent > 0
ERROR: column "chk_parent" does not exist at character 2342
12 matches
Mail list logo
