By: maxi_million

maxi_million — Fri, 17 Feb 2006 07:03:31 +0000

in fact theres another problem with another class that comes with DB_Table package called DB_Table_Manager

what interests me here is this cool method: create()

all very neat and convenient…just pass the params and it tries to create the table for you also…

TILL you come to around line 204…its horror!
$newIdxName = $table . ‘_’ . $idxname . ‘_idx’;

and then..line 208…
if (strlen($newIdxName) > 30) {
return DB_Table::throwError(
DB_TABLE_ERR_IDX_STRLEN,
“‘$idxname’ (’$newIdxName’)”
);
}

its all very good it tries to take care of possible errors in oracle and pgsql…
but what about us poor souls with mysql…

i did the despicable thing…simply commented out that portion…but any better alternatives…

i mean you may sometimes get a littele prosaic and give a lonfg name to your table…but hardly expect to be rewarded with a PEAR error

By: maxi_million

maxi_million — Fri, 17 Feb 2006 06:45:52 +0000

reg: Problem with AUTO_INCREMENT

faced the same problem myself. i found a neat solution…atleast works fine with me…
made a class called DB_Table_Mod
and rewritten the nextID() function to return the next autoincrement value. the function simply returns the max value + 1
of course my other classes extends or needs an object of DB_Table_Mod

Comments on: DB_Table Problem

By: maxi_million

By: maxi_million