Subject | Re: [Firebird-Architect] Re: C API Upgrade? |
---|---|
Author | marius popa |
Post date | 2008-01-31T09:33:43Z |
On Jan 31, 2008 10:21 AM, Alex Peshkov <peshkoff@...> wrote:
I thought ibpp functions could be exported
Another problem with changing the api is that it can be messy
I'm thinking on the php mysql driver as an wrong example
there are 4-5 drivers that are out there
1. mysql classic http://us.php.net/mysql
2. mysqli for enhanced functionality
http://us.php.net/manual/en/ref.mysqli.php
3. mysl-nd rewriten driver
http://dev.mysql.com/downloads/connector/php-mysqlnd/
4. mysl-pdo http://usphp.com/manual/en/ref.pdo-mysql.php
5. pear-mdb2 http://pear.php.net/package/MDB2_Driver_mysql
So rewriting the api/drivers can be messy and can bring an hairy complexity
and can kill backward compatibility
I wonder if it was better to have an single jdbc like standard like in Java
Php is going on the java territory anyway (pdo1-2 is supported somehow by
ibm, oracle, mysql)
So if we change the api is better to choose an standard that can be used on
any language and actively used
(jdbc is an good start)
odbc seems to be used and is stable but somehow killed by microsoft (they
push ado , .net)
developer flamerobin.org
[Non-text portions of this message have been removed]
> On Thursday 31 January 2008 11:14, marius popa wrote:Ok then :)
> > > Can you provide a list of functions you suggest?
> >
> > or another way would be to use ibpp.org
>
> Sorry, we need not ++only API.
I thought ibpp functions could be exported
Another problem with changing the api is that it can be messy
I'm thinking on the php mysql driver as an wrong example
there are 4-5 drivers that are out there
1. mysql classic http://us.php.net/mysql
2. mysqli for enhanced functionality
http://us.php.net/manual/en/ref.mysqli.php
3. mysl-nd rewriten driver
http://dev.mysql.com/downloads/connector/php-mysqlnd/
4. mysl-pdo http://usphp.com/manual/en/ref.pdo-mysql.php
5. pear-mdb2 http://pear.php.net/package/MDB2_Driver_mysql
So rewriting the api/drivers can be messy and can bring an hairy complexity
and can kill backward compatibility
I wonder if it was better to have an single jdbc like standard like in Java
Php is going on the java territory anyway (pdo1-2 is supported somehow by
ibm, oracle, mysql)
So if we change the api is better to choose an standard that can be used on
any language and actively used
(jdbc is an good start)
odbc seems to be used and is stable but somehow killed by microsoft (they
push ado , .net)
>--
>
>
> Yahoo! Groups Links
>
>
>
>
developer flamerobin.org
[Non-text portions of this message have been removed]