I think this is a funny bug:
select ('TRUE'::TEXT)::BOOL;
bool
--
f
but:
select ('TRUE'::varchar(4))::BOOL;
bool
--
t
or
select ('true'::TEXT)::BOOL;
bool
--
t
My postgresql version:
PostgreSQL 8.3.4
Laczi József
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
Hello
It works on my server. Do you have a some specific configuration?
postgres=# select ('true'::text)::bool;
bool
--
t
(1 row)
I am checked 8.3, 8.4, 9.0.
Regards
Pavel Stehule
2010/3/18 Laczi József :
> I think this is a funny bug:
>
> select ('TRUE'::TEXT)::BOOL;
> bool
> --
> f
On Thu, Mar 18, 2010 at 11:37:53AM +0100, Pavel Stehule wrote:
> postgres=# select ('true'::text)::bool;
> bool
> --
> t
> (1 row)
>
> I am checked 8.3, 8.4, 9.0.
What about the 'TRUE' (all caps) case? Note the blow:
> 2010/3/18 Laczi József :
> > I think this is a funny bug:
> >
> > selec
The following bug has been logged online:
Bug reference: 5378
Logged by: lsasha
Email address: sasha.mail...@gmail.com
PostgreSQL version: 8.4.2
Operating system: Windows 7
Description:Little inaccuracy in the manual
Details:
Manual for PostgreSql 8.4 cantains a lit
The following bug has been logged online:
Bug reference: 5377
Logged by: michel rosa
Email address: mr...@geomatic.ch
PostgreSQL version: 8.3.10
Operating system: debian
Description:group by problem
Details:
Hello,
I have the following problem
select to_char(uplo
"michel rosa" wrote:
> I get extras rows for 2010-03-02
I'm not sure I understand your concern.
Is it that the result set includes these rows?:
> to_char | cost | count
> +--+---
> 2010-03-02 | 2.0 | 7
> 2010-03-02 | 3.0 | 3
What do you get from?:
sel
=?ISO-8859-2?Q?Laczi_J=F3zsef?= writes:
> I think this is a funny bug:
> select ('TRUE'::TEXT)::BOOL;
> bool
> --
> f
Works here:
regression=# select ('TRUE'::TEXT)::BOOL;
bool
--
t
(1 row)
(I'm checking 8.3.10, but that code hasn't changed in a long time.)
Maybe you have created
"michel rosa" writes:
> ...
> and upload_date<='2010-03-02'
> give as result
> 2010-03-02 |0 | 837
> 2010-03-02 | 0.5 | 136
> 2010-03-02 | 1.5 | 138
> but when upload_date<='2010-03-03', I get extras rows for 2010-03-02
Is the upload_date column actually a date? I think maybe i
"lsasha" writes:
> Manual for PostgreSql 8.4 cantains a little inaccuracy in
> the Table 9.47. Session Information Functions chapter:
> current_query instead of current_query()
Hmm. Normally we're not very picky about that, but in that particular
table I guess we need to be, since some of the ot
My database implements partitioning using inheritance and constraint exclusion,
as described in the fine manual. Each partition holds data for a single day,
and there are well over 300 child partitions.
The exception mentioned below notwithstanding, the technique works exceedingly
well and i
Bob Lunney writes:
> 1. A select into query is run which summarizes the data from a partition
> into a table outside the inheritance hierarchy, which is then indexed.
> 2. Then
> a. a transaction is begun,
> b. the original partition is dropped,
> c. the new table renamed to the orig
The following bug has been logged online:
Bug reference: 5379
Logged by: Hyunsik Choi
Email address: hyunsik.c...@gmail.com
PostgreSQL version: 8.4
Operating system: Ubuntu Linux 9.10 and Gentoo Linux
Description:Adding hunspell-ko dictionary for full-text search
does
So I did miss something! Thanks for the brilliant explanation and simple
solution, Tom.
Bob
--- On Thu, 3/18/10, Tom Lane wrote:
> From: Tom Lane
> Subject: Re: [BUGS] Error while altering an inheritance hierarchy in mid-query
> To: "Bob Lunney"
> Cc: pgsql-bugs@postgresql.org
> Date: Thurs
13 matches
Mail list logo
