headers
Pavel Cisar | 2 Dec 15:01
Picon

Future for Python driver

Hi all,

Those who attended my "Python drivers" session at conference in
Luxembourg already know that last two months I have worked on another
Python driver for Firebird (codename fdb). It was just an experiment how
far I could go in short time with another approach to implementation,
not real attempt to replace both existing drivers (KInterbasDB and
firebirdsql). However, it went so well, that we have a real chance to
get out a truly universal pure Python driver for Firebird next year.
Here are details...

The *fdb* driver is based on my old experiments (back in 2009) with
ctypes interface to Firebird. Back then it ended with ibase.py interface
and very basic connection and transaction classes, and ability to make a
connection and start a transaction. Over last month I was able to
implement full DB API 2.0 Spec + some extra.

- Connection, including drop and create database
- Transaction, incl. multiple transaction per connection, transaction
parameters, savepoints and retaining.
- Cursor. Fully supports materialized BLOBs, input parameters (incl.
BLOBs), should handle dialect 1 gracefully (but it wasn't thoroughly
tested), has row mappings and iterator protocol support built-in,
automatic unicode/connection charset conversions.
- Services. All what KInterbasDB 3.3.0 supports (i.e. all except TRACE).

What is missing:

- Prepared Statements (some work done, but unfinished).
- db_info API calls
(Continue reading)

Permalink | Reply |
headers
Philippe Makowski | 2 Dec 15:19

Re: Future for Python driver

Pavel Cisar  [2011-12-02 15:01] :
> So, that's the current situation and plans for future. Any comments are
> welcome...
that's good news and perspectives

hope that we all go this way

to help sharing the code, I would vote to have a git or mercurial
repository, not svn

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/firebird-python/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/firebird-python/join
    (Yahoo! ID required)

<*> To change settings via email:
    firebird-python-digest@... 
    firebird-python-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    firebird-python-unsubscribe@...
(Continue reading)

Permalink | Reply |
headers
werner | 2 Dec 16:12
Picon
Favicon

Re: Future for Python driver

Hi Pavel,

On 12/02/2011 03:01 PM, Pavel Cisar wrote:
...
> So, that's the current situation and plans for future. Any comments are
> welcome...
>
Excellent news!

Werner

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/firebird-python/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/firebird-python/join
    (Yahoo! ID required)

<*> To change settings via email:
    firebird-python-digest@... 
    firebird-python-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
(Continue reading)

Permalink | Reply |
headers
Mario Lacunza | 2 Dec 16:34
Picon
Gravatar

Re: Future for Python driver

Hello,

First of all: its a great new! for some problems wit the old driver and 
not new dev job with the actuals I need to take the decision of migrate 
to other DB for most of my projects.

Pavel I think your idea is nice, Im expecting the opinion from the dev 
of the other driver. In my point of view have 3 drivers for KI is too 
much I think keep one and strong one is the best idea.

I can help in the test phase if thats necessary.

Saludos / Best regards

Mario Lacunza
Email:: mlacunza@...
Personal Website:: http://www.lacunza.biz/
OpenOffice.org:: http://es.openoffice.org/
OpenOffice.org Perú:: http://openoffice-peru.com/
Hosting:: http://mlv-host.com/
Mascotas Perdidas:: http://mascotas-perdidas.com/
Google Talk: mlacunzav Skype: mlacunzav
MSN: mlacunzav@... Y! messenger: mlacunzav

On 02/12/11 09:01, Pavel Cisar wrote:
> Hi all,
>
> Those who attended my "Python drivers" session at conference in
> Luxembourg already know that last two months I have worked on another
> Python driver for Firebird (codename fdb). It was just an experiment how
(Continue reading)

Permalink | Reply |
headers
Hajime Nakagami | 3 Dec 01:33
Picon

Re: Future for Python driver

It's good news.

firebirdsql driver can not support embedded FB.
But it works on cpython(2 and 3), iron python , pypy, jython.

I think many approach is good for everyone.

I hope fdb's code repository deploy github or bitbucket

2011/12/2 Pavel Cisar <pcisar@...>:
> Hi all,
>
> Those who attended my "Python drivers" session at conference in
> Luxembourg already know that last two months I have worked on another
> Python driver for Firebird (codename fdb). It was just an experiment how
> far I could go in short time with another approach to implementation,
> not real attempt to replace both existing drivers (KInterbasDB and
> firebirdsql). However, it went so well, that we have a real chance to
> get out a truly universal pure Python driver for Firebird next year.
> Here are details...
>
> The *fdb* driver is based on my old experiments (back in 2009) with
> ctypes interface to Firebird. Back then it ended with ibase.py interface
> and very basic connection and transaction classes, and ability to make a
> connection and start a transaction. Over last month I was able to
> implement full DB API 2.0 Spec + some extra.
>
> - Connection, including drop and create database
> - Transaction, incl. multiple transaction per connection, transaction
> parameters, savepoints and retaining.
(Continue reading)

Permalink | Reply |
headers
mariuz | 5 Dec 16:41
Picon
Favicon

Re: Future for Python driver

On Fri, Dec 02, 2011 at 03:01:37PM +0100, Pavel Cisar wrote:
> Hi all,
> 
> Those who attended my "Python drivers" session at conference in
> Luxembourg already know that last two months I have worked on another
> Python driver for Firebird (codename fdb). It was just an experiment how
> far I could go in short time with another approach to implementation,
> not real attempt to replace both existing drivers (KInterbasDB and
> firebirdsql). However, it went so well, that we have a real chance to
> get out a truly universal pure Python driver for Firebird next year.
> Here are details...
> 
> The *fdb* driver is based on my old experiments (back in 2009) with
> ctypes interface to Firebird. Back then it ended with ibase.py interface
> and very basic connection and transaction classes, and ability to make a
> connection and start a transaction. Over last month I was able to
> implement full DB API 2.0 Spec + some extra.
> 
> - Connection, including drop and create database
> - Transaction, incl. multiple transaction per connection, transaction
> parameters, savepoints and retaining.
> - Cursor. Fully supports materialized BLOBs, input parameters (incl.
> BLOBs), should handle dialect 1 gracefully (but it wasn't thoroughly
> tested), has row mappings and iterator protocol support built-in,
> automatic unicode/connection charset conversions.
> - Services. All what KInterbasDB 3.3.0 supports (i.e. all except TRACE).
> 
> What is missing:
> 
> - Prepared Statements (some work done, but unfinished).
(Continue reading)

Permalink | Reply |
headers
Maximiliano Robaina | 7 Dec 21:13
Picon
Favicon

Re: Future for Python driver

El vie, 02-12-2011 a las 15:01 +0100, Pavel Cisar escribió:
> Hi all,
> 
> Those who attended my "Python drivers" session at conference in
> Luxembourg already know that last two months I have worked on another
> Python driver for Firebird (codename fdb). It was just an experiment how
> far I could go in short time with another approach to implementation,
> not real attempt to replace both existing drivers (KInterbasDB and
> firebirdsql). However, it went so well, that we have a real chance to
> get out a truly universal pure Python driver for Firebird next year.
> Here are details...
> 
> The *fdb* driver is based on my old experiments (back in 2009) with
> ctypes interface to Firebird. Back then it ended with ibase.py interface
> and very basic connection and transaction classes, and ability to make a
> connection and start a transaction. Over last month I was able to
> implement full DB API 2.0 Spec + some extra.
> 
> - Connection, including drop and create database
> - Transaction, incl. multiple transaction per connection, transaction
> parameters, savepoints and retaining.
> - Cursor. Fully supports materialized BLOBs, input parameters (incl.
> BLOBs), should handle dialect 1 gracefully (but it wasn't thoroughly
> tested), has row mappings and iterator protocol support built-in,
> automatic unicode/connection charset conversions.
> - Services. All what KInterbasDB 3.3.0 supports (i.e. all except TRACE).
> 
> What is missing:
> 
> - Prepared Statements (some work done, but unfinished).
(Continue reading)

Permalink | Reply |

Gmane