consider the following
create table TARRBINT ( RNUM integer not null , CARRBINT bigint array[5] )
;
Can someone clarify why Postgres does not like examples 2, 6 and 7
1.insert into TARRBINT(RNUM, CARRBINT) values ( 0, null);
2.insert into TARRBINT(RNUM, CARRBINT) values ( 0, ARRAY[]);
3.insert
n, c3 turkish etc names
vs
create table TKO (c1 char(...)), create table TTH (c1 char (...))
vs
different databases etc
On Mon, Dec 7, 2009 at 4:20 PM, the6campbells wrote:
> so where would I define something akin to what I can do in DB2 LUW where
> collate using system means to sort by the
:
> the6campbells writes:
> > Just want to clarify if there is something I've overlooked or if this is
> a
> > known issue in PG 8.4 and 8.3
>
> > CREATE DATABASE test
> > WITH OWNER = postgres
> >ENCODING = 'UTF8'
> >LC_COLLATE =
Just want to clarify if there is something I've overlooked or if this is a
known issue in PG 8.4 and 8.3
CREATE DATABASE test
WITH OWNER = postgres
ENCODING = 'UTF8'
LC_COLLATE = 'English, United States, UTF-8'
LC_CTYPE = 'English, United States, UTF-8'
select ('İsteği')
Why is Postgres returning a timestamp instead of the expected date data type
for the first expression (the second returns a date)?
In other words, is this a known bug or is it design intent. The manuals did
not seem to appear to say this is intentional behaviour but is not SQL
standard.
select da
Question.. is there a way that I can get Postgres to return the tz as
supplied on the insert statement
insert into TTSTZ(RNUM, CTSTZ) values ( 0, null);
insert into TTSTZ(RNUM, CTSTZ) values ( 1, timestamp with time zone
'2000-12-31 12:00:00.0-05:00');
insert into TTSTZ(RNUM, CTSTZ) values ( 2, ti
the db2 family does not
On Sun, Oct 4, 2009 at 2:10 AM, Thomas Kellerer wrote:
> the6campbells wrote on 29.09.2009 04:54:
>
>> 2. Do you intend to remove the requirement to include the recursive
>> keyword - as other vendors allow
>>
>
> The standard *requires*
Couple of questions:
1. Why does Postgres not throw a parsing error during sqlPrepare for this
statement vs at sqlExecute
with t_cte ( c1, ctr ) as (
select 1,0 from tversion union
select 2,0 from tversion union all
select c1, ctr + 1 from t_cte where c1=1 and ctr < 5 union all
select c1, ctr + 1