RE: [PHP] Re: [PHP-DB] Re: [PHP] Re: Cross DB application
| From: | SP | Date: | Sat, 20 Apr 2002 21:03:30 +0000 |
| Subject: | RE: [PHP] Re: [PHP-DB] Re: [PHP] Re: Cross DB application | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-93839@lists.php.net to get a copy of this message | ||
Thanks Richard, just starting out but keeping portability in the back of my
mind. I've been keeping the sql statements standard and doing everything
through php so I don't get caught when moving to another database.
-----Original Message-----
From: Richard Ellerbrock [mailto:richarde@eskom.co.za]
Sent: April 20, 2002 8:18 AM
To: php-general@lists.php.net
Subject: [PHP] Re: [PHP-DB] Re: [PHP] Re: Cross DB application
On Thu, 18 Apr 2002 16:05:13 +0200, Manuel Lemos wrote:
> Hello,
>
> Sp wrote:
>>
>> Hi Manuel, I still don't see a problem in others telling their
>> experiences with certain packages. If someone has just used metabase
>> or has just used adodb then I would like to hear how easy/hard it was
>> to port to another database.
>
> Sure, but what I meant is that since most people only have experienced
> one or the other, you only hear from people that can't compare both.
>
> If you want to hear experiences of people that tried Metabase, try
> asking in Metabase mailing list (
> http://groups.yahoo.com/group/metabase-dev/ ) or BinaryCloud
> mailing
> lists (
> http://binarycloud.tigris.org/servlets/ProjectMailingListList ).
> I think Alex Black (BinaryCloud project leader) has tried both MySQL and
> Oracle with Metabase.
I have done MySQL (MyISAM, INNODB), PostgreSQL and Oracle 9i with AdoDB -
see http://iptrack.sourceforge.net. Works just fine for
me. The hardest
part was to get around limitations of certain databases - like Oracle
does no support record count. This is not impossible to get around, but
when you are used to making use of these standard features of other
databases, it takes a bit of getting used to. Other issues are syntax
issues - you cannot use any funky functions which are unique to your dbf.
Also, you must write very standard SQL - no shortcuts. For example, with
Oracle you MUST specify the table name throughout your query when doing
joins, even if the column is unambiguos.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php