Skip site navigation (1) Skip section navigation (2)

Re: About pyvertica (a clone of pyscopg2)

From: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>
To: Federico Di Gregorio <fog(at)initd(dot)org>
Cc: Angel Freire <cuerty(at)gmail(dot)com>, psycopg(at)postgresql(dot)org
Subject: Re: About pyvertica (a clone of pyscopg2)
Date: 2011-09-07 09:38:52
Message-ID: CA+mi_8baXqinV=V_oUw6VENqzCid50TnvOT9-NZFwZ3jPNtGOw@mail.gmail.com (view raw or flat)
Thread:
Lists: psycopg
On Wed, Sep 7, 2011 at 10:12 AM, Federico Di Gregorio <fog(at)initd(dot)org> wrote:
> Hi Angel,
>
> I hope you don't bother I added the psycopg mailing list in cc: other
> people can be interested in your work. :)
>
> On 06/09/11 20:22, Angel Freire wrote:
>> Hi, my name is Angel and since a few weeks now I've been working with
>> some database engine called "Vertica" it's a column-oriented db based
>> on PostgreSQL, it's so based on PostgresSQL that with a few little
>> modifications pyscopg2 is able to connect to it and perform queries
>> without any problems. I've found the patch needed to make pyscopg2 run
>> with Vertica in StackOverflow
>> (http://stackoverflow.com/questions/2469167/merge-excel-cells-using-pyexcelerator).
>
> I can't find a patch there. :(

It may have been this:

http://stackoverflow.com/questions/2695684/using-an-odbc-application-with-a-jdbc-driver

Looks like Vertica has a few differences in the types oid.
Unfortunately there is at least a conflict: from the patch I see oid
16 is used by Vertica as a decimal type, while Postgres uses the same
oid for the bool type. A solution could be to detect vertica at
connection time (which seems done by checking server_version = 0, I
don't know if there is a more robust way) and re-organize the
typecaster map accordingly.

-- Daniele

In response to

Responses

psycopg by date

Next:From: Federico Di GregorioDate: 2011-09-07 09:52:23
Subject: Re: About pyvertica (a clone of pyscopg2)
Previous:From: Federico Di GregorioDate: 2011-09-07 09:12:13
Subject: Re: About pyvertica (a clone of pyscopg2)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group