Craig,
I know it's not what you want (Pg behaving how you expect out of the
box) but creating implicit casts to the desired types will resolve
your immediate issue. You still have to run some Pg-specific code, but
it can be restricted to your DDL where there's (presumably) already
plenty.
My
value in step 3
There is no ambiguity or magic to happen. Obviously in PG case there is
some design or fault somewhere in this use-case when distinct keyword
is used and is processed in step 2, that's all.
Farid
On 6/4/2010 10:41 PM, Greg Stark wrote:
On Fri, Jun 4, 2010 at 11:15 PM, Farid
Ringer wrote:
On 05/06/10 06:15, Farid Zidan wrote:
insert into test_insert
(col1, col2)
select *distinct*
'b',
'2010-04-30 00:00:00'
Does not work. That's a bug.
Not really.
select distinct * from (VALUES
('b','2010-04-30 00:00:00'),
('b','2010-04-30
Dimitri
This is the last you will hear from me about this issue. I would have
stopped repsonding long time ago, but I kept getting responses that
required reply. Do not knock on the door if you don't want someone to
answer the door.
There is no point in spending more of my time explaining
The following bug has been logged online:
Bug reference: 5490
Logged by: Farid Zidan
Email address: fa...@zidsoft.com
PostgreSQL version: 8.4.1
Operating system: Windows XP 32-bit
Description:Using distinct for select list causes insert of
timestamp string literal
PostgreSQL
compatibility with SQL standard and interoperability with generic sql
statements.
best regards,
Farid
On 6/4/2010 11:57 AM, Kevin Grittner wrote:
"Farid Zidan" fa...@zidsoft.com wrote:
insert into test_insert
(col1, col2)
select distinct
'b',
'2010-04-30 00:00:00'
On 6/4/2010 12:52 PM, Kevin Grittner wrote:
Farid Zidan fa...@zidsoft.com wrote:
If we were strictly complying with the SQL standard,
Considering the statement works in all the 9 DBMS systems+ that I
have tested so far as mentioned
developers projects and it
would need to be addressed at
some point in the future with a solution where it just work like it
does in all the other DBMSs.
Farid
On 6/4/2010 1:36 PM, Kevin Grittner wrote:
Farid Zidan fa...@zidsoft.com wrote:
can be eliminated
e subquery!)
Farid
On 6/4/2010 4:18 PM, Greg Stark wrote:
On Fri, Jun 4, 2010 at 7:18 PM, Farid Zidan fa...@zidsoft.com wrote:
If a simple SQL statement works on 9+ different databases
For what it's worth are you sure it works as you expect in these other
databases?
I su
Title: Signature
Hello Kevin,
I can't help but wonder why you resist using the standard syntax.
I am using the standard syntax. Single quote in sql denotes a string.
so '2010-04-30 00:00:00' is string literal. That's universal. Now you
want me to use PG-specific timestamps and that's
The following bug has been logged online:
Bug reference: 1415
Logged by: Farid Zidan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows 2000
Description:odbc driver SQLGetInfo SQL_CATALOG_TERM returns empty
string
Details:
odbc
The following bug has been logged online:
Bug reference: 1422
Logged by: Farid Zidan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows 2
Description:ODBC SQLTables SQL_ALL_TABLE_TYPES no resultset
Details:
::SQLTables( hstmt
The following bug has been logged online:
Bug reference: 1423
Logged by: Farid Zidan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows 2000
Description:ODBC SQLTables SQL_ALL_CATALOGS and SQL_ALL_SCHEMAS
options don't work
Details
13 matches
Mail list logo
