Tom Lane wrote:
> I think you need to file a bug with Zeos to fix whatever their problem
> is with text.
Well, to be fair, type text is not SQL standard. But surely Zeos won't get
very far with this superstrict typing approach. At least a little bit more
context might help us understand.
--
Hi Alvaro
On Fri, Mar 28, 2008 at 6:05 PM, Alvaro Herrera <[EMAIL PROTECTED]>
wrote:
> NikhilS escribió:
>
> > I will take a look at the pg_dump related changes if you want. We will
> need
> > changes in flagInhAttrs() and in getTableAttrs() to query the backend
> for
> > these 2 attributes for p
Peter Eisentraut wrote:
> Tom Lane wrote:
> > I think you need to file a bug with Zeos to fix whatever their
> > problem is with text.
>
> Well, to be fair, type text is not SQL standard. But surely Zeos
> won't get very far with this superstrict typing approach. At least a
> little bit more con
e was checked by ESET NOD32 Antivirus.
http://www.eset.com
__ Information from ESET NOD32 Antivirus, version of virus signature
database 2994 (20080402) __
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@post
Pedro Gimeno escribió:
> Zeos (as well as the Borland Database Engine, which it just mimics in
> this sense) assumes that VARCHAR fields in general (not just
> PostgreSQL's) are textual fields with a limit of 255 characters for all
> supported servers, which are graphically associated with single
Alvaro Herrera wrote:
> Pedro Gimeno escribió:
>
>> Zeos (as well as the Borland Database Engine, which it just mimics in
>> this sense) assumes that VARCHAR fields in general (not just
>> PostgreSQL's) are textual fields with a limit of 255 characters for all
>> supported servers, which are grap
"Pavel Golub" <[EMAIL PROTECTED]> writes:
> Comparing 8.3.1 to 8.2.5 release INSERT of >1000 rows is very slow.
> INSERT INTO numbers (numberint, numberstr) VALUES (1, 'One');
> INSERT INTO numbers (numberint, numberstr) VALUES (2, 'Two');
> INSERT INTO numbers (numberint, numberstr) VALUES (3, 'T
The following bug has been logged online:
Bug reference: 4084
Logged by: Premysl Paska
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.15
Operating system: Linux
Description:Some DST timezones switche to summer time (one week)
later
Details:
We use TIMESTAP
The following bug has been logged online:
Bug reference: 4085
Logged by: Jeff Dwyer
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: Mac OS X
Description:No implicit cast after coalesce
Details:
This works fine:
select 1 where current_dat
Jeff Dwyer wrote:
> This works fine:
> select 1 where current_date between '1900-3-3' and '1900-2-2';
> This doesn't:
> select 1 where current_date between coalesce(null,current_date) and
> coalesce(null, '1900-1-2');
>
> This fix works:
> select 1 where current_date between coalesce(null,current_
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Jeff Dwyer wrote:
>> This seems like a bug to me. Why should an explicit cast be necessary after
>> a coalesce?
> Because coalesce(null, '1900-1-2') has no other type information attached, so
> it would have picked text by default as result type, and
11 matches
Mail list logo
