zend+pdo+db2

[Christian Welzel]

Hi there,

i'm not sure, if it is a php or a database problem, but i would
consider it the first.
i'm programming some code with zend_db and pdo to access a db2
database. additionally a want to be able to replace the db2 on the
localhost with mysql (easier to maintain for a developer). This should
be no problem, as long as i stick to ansi-sql...
But now my problem arises:
I initialize my table-classes in zend like this:

class Core_Db_Table_Actions extends Zend_Db_Table_Abstract
{
protected $_name = 'actions';
}

this works fine on mysql but db2 is compaining about the not
defined table "actions". If i write it all uppercase (ACTIONS)
db2 is happy...
So i wonder if it shouldn't be the task of zend/pdo to hide those
differences from the programmer? Or have i overseen or misunderstood
something?

--
MfG, Christian Welzel aka Gawain@Regenbogen

GPG-Key: http://www.camlann.de/key.asc
Fingerprint: 4F50 19BF 3346 36A6 CFA9 DBDC C268 6D24 70A1 AD15

[Jerry Stuckle]

Christian Welzel wrote:

Hi there,

i'm not sure, if it is a php or a database problem, but i would
consider it the first.
i'm programming some code with zend_db and pdo to access a db2
database. additionally a want to be able to replace the db2 on the
localhost with mysql (easier to maintain for a developer). This should
be no problem, as long as i stick to ansi-sql...
But now my problem arises:
I initialize my table-classes in zend like this:

class Core_Db_Table_Actions extends Zend_Db_Table_Abstract
{
protected $_name = 'actions';
}

this works fine on mysql but db2 is compaining about the not
defined table "actions". If i write it all uppercase (ACTIONS)
db2 is happy...
So i wonder if it shouldn't be the task of zend/pdo to hide those
differences from the programmer? Or have i overseen or misunderstood
something?

Nope. Identifiers in SQL are case sensitive. And if you're running
MySQL on Linux instead of Windows, you'll find the table names are case
sensitive there, also (if you take the defaults).

The non-standard operation here is MySQL not having case sensitive table
names on Windows.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attglobal.net
==================

[Christian Welzel]

Jerry Stuckle schrieb:

Nope. Identifiers in SQL are case sensitive. And if you're running
MySQL on Linux instead of Windows, you'll find the table names are case
sensitive there, also (if you take the defaults).

Thanks for your advise. I never hit this problem before, because i always
create tables lowercase. But now the mtk from ibm created them in uppercase...
So this confused me a bit.

--
MfG, Christian Welzel aka Gawain@Regenbogen

GPG-Key: http://www.camlann.de/key.asc
Fingerprint: 4F50 19BF 3346 36A6 CFA9 DBDC C268 6D24 70A1 AD15

[Jerry Stuckle]

Christian Welzel wrote:

Jerry Stuckle schrieb:

>Nope. Identifiers in SQL are case sensitive. And if you're running
MySQL on Linux instead of Windows, you'll find the table names are
case sensitive there, also (if you take the defaults).

Thanks for your advise. I never hit this problem before, because i always
create tables lowercase. But now the mtk from ibm created them in
uppercase...
So this confused me a bit.

Yep, it's all a matter of style, just like variable names in PHP. But,
like variable names, case is important.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attglobal.net
==================