PEAR Bug Search Results

DB_DataObject: Documentation Problem 16708 [Open] SequenceKey() Required When Not Using INI

balexander at visionpointsystems dot com — 2009-10-17T22:51:31+00:00

DB_DataObject Documentation Problem
Reported by mabgfounder
2009-10-17T22:51:31+00:00
PHP: 5.3.0 OS: Windows XP Package Version: 1.8.12

Description:
------------
First off - thanks for maintaining what appears to be a nice db object library. When working from INI files it was easy to get started and worked right out of the box.

However, when I tried to make classes from scratch, using the docs as a guide, I did not realize that sequenceKey() existed nor how critical it was for things to work correctly.

BTW: These are the docs I was using:
http://pear.php.net/manual/en/package.database.db-dataobject.intro-autobuilding.php

I had no reason for the application's account on mysql to be able to create tables (that I knew of) so I did not grant those permissions. Inserts started failing because of an inability to create {tablename}_seq.

I did eventually figure out that a missing sequenceKey() implementation was the problem, and after some experimentation appear to have figured out how to correctly implement it. However, a lot of time would have been saved at it been in the documentation.

Thanks again for all of your time and help. This seems to be a really great library.

Test script:
---------------
You should be able to use the example on the page I listed with a mysql database where the user does not have table create permissions granted.

Expected result:
----------------
Inserts and updates will fail

DB_DataObject: Feature/Change Request 14794 [Open] UTF8 Support for MYSQL database

bernhard dot picher at chello dot at — 2008-10-14T09:01:25+00:00

DB_DataObject Feature/Change Request
Reported by repher
2008-10-14T09:01:25+00:00
PHP: 5.2.6 OS: irrelevant Package Version: 1.8.8

Description:
------------
Mysql does not use utf8 by default. Since i almost never use anything 
else than utf8, i have to modify the DB_DataObject class everytime to 
execute a 
'set names utf8' query at the end of the _connect function. Maybe we 
should consider implementing a feature to check if there is for 
example a 
'mysql_client_encoding' option in the options.

I have implemented a simple addition to _connect to solve this 
problem:

if (isset($_DB_DATAOBJECT['CONFIG']['mysql_client_encoding'])) {
  if ($_DB_DATAOBJECT['CONNECTIONS'][$this->_database_dsn_md5]-
>dsn['phptype'] == 'mysqli') {
    $_DB_DATAOBJECT['CONNECTIONS'][$this->_database_dsn_md5]-
>query("SET NAMES " . 
$_DB_DATAOBJECT['CONFIG']['mysql_client_encoding'] );
  }
}

DB_DataObject: Bug 13934 [Open] Problem with MDB2 and getListOf()

nahuel at ahtna dot org — 2008-09-17T18:47:04+00:00

DB_DataObject Bug
Reported by nahuel
2008-05-18T17:23:32+00:00
PHP: 5.2.0 OS: Linux Package Version: 1.8.8

Description:
------------
I tryied to reload the configuration, with ->databaseStructure()
and an error was expected. I use MDB2.

Test script:
---------------
$db->databaseStructure("mysql://user:pass@localhost/database");

Actual result:
--------------
Fatal error: Call to undefined function: MDB2_Driver_mysql::getListOf(). in /usr/share/php/MDB2.php on line 1936

DB_DataObject: Feature/Change Request 13843 [Open] $_query property not properly restored in fetch()

markus at fischer dot name — 2008-05-06T09:26:12+00:00

DB_DataObject Feature/Change Request
Reported by markus
2008-05-06T08:39:45+00:00
PHP: 5.2.5 OS: Linux Package Version: 1.8.8

Description:
------------
In fetch(), is there a reason why the $_query property is not restored to its initial value after the last row has been fetched in DB_DataObject::fetch() on line 550?

The property is set to false [line 575] to indicate there is more data to fetch, but after the last row has been fetched there is no reason to keep the DataObject from being reused as far as we can see.

The process of backing up $_query and restoring it is applied successfully in the find() method (see line 410 and 468).

DB_DataObject: Feature/Change Request 13798 [Open] Field length validation

2008-04-29T04:28:34+00:00

DB_DataObject Feature/Change Request
Reported by davidsimpson
2008-04-29T04:28:34+00:00
PHP: 5.1.4 OS: Windows/ Linux/ Solaris Package Version: 1.8.8

Description:
------------
Would it be possible to add the field length information (currently shown in the comments added to the DB DataObject class files) to an associative array (fieldname => length), to allow for some simple data validation?

In particular this would be useful for varchar fields where the DataObject validation could be used prior to attempting to update the database.

I know that Request #6431 was for similar information and has been set to "Wont fix", but it would be much nicer to be able to hold the field lengths in the data object, as otherwise we either have to query the tableinfo on every update/insert, or catch errors from the database - neither of which seem particularly efficient?

Thanks for all your hard work on DB_DataObject - we have found it to be extremely useful in a number of projects now, using a variety of backend databases (mysql, oracle and postgres).

Test script:
---------------
For example, in the _generateClassTable function 

prior to processing the columns add:

$fieldMaxLen = array();

while processing each column add:

if (isset($t->len) && ($t->type=="VARCHAR")) {
  $fieldMaxLen[] = "\"{$t->name}\" => {$t->len}";
}

and following the loop add:

$body .= "    // Array of varchar field max lengths for simple validation\n";
$body .= "    protected \$varcharsMax = array(".join($fieldMaxLen, ",\n\t\t\t\t\t\t\t\t\t").");";

DB_DataObject: Documentation Problem 13656 [Verified] Undocumented CONFIG var quote_identifiers_tableinfo

adam dot setzler at gmail dot com — 2008-09-17T18:46:40+00:00

DB_DataObject Documentation Problem
Reported by adamsetzler
2008-04-12T12:14:16+00:00
PHP: 5.2.5 OS:  Package Version: 1.8.8

Description:
------------
Not having "quote_identifiers_tableinfo = 1" causes problems with MDB2 and certain table names.  There is no documentation of this feature outside the code itself.

DB_DataObject: Documentation Problem 12694 [Verified] $object->update($original);

alexor_patator at yahoo dot fr — 2009-10-15T08:17:55+00:00

DB_DataObject Documentation Problem
Reported by banquette
2007-12-14T16:15:37+00:00
PHP: 5.2.5 OS: Windows Package Version: 1.8.7

Description:
------------
As a user said on the "update()" page (http://pear.php.net/manual/en/package.database.db-dataobject.db-dataobject.update.php) :

When called with

$object->update($original);

this function appears to return true rather than 0 if no rows are affected.

Expected result:
----------------
Should return 0 (as no row affected)

Actual result:
--------------
return true

DB_DataObject: Bug 12550 [Open] Updating a record to set a field null

andrew dot nagy at villanova dot edu — 2009-11-03T04:51:05+00:00

DB_DataObject Bug
Reported by asnagy
2007-11-29T08:49:09+00:00
PHP: 5.2.2 OS: linux Package Version: 1.8.7

Description:
------------
I am trying to update a record and set a foreign key to "null" however when i call the update method (with debug set on) I see that it tries to set the value to "0" and not "null"

Test script:
---------------
// Unjoin the User from the Tags
$join = new Resource_tags();
$join->user_id = $this->id;
$join->resource_id = $resource->id;
if ($join->find(true)) {
    $join->user_id = 'null';
    $join->update();
}

Expected result:
----------------
update resource_tags set user_id = null ...

Actual result:
--------------
update resource_tags set user_id = 0 ...

DB_DataObject: Feature/Change Request 11081 [Verified] Support for createTables on Postgres with views in schema

senna at mugeso dot com — 2008-02-27T01:12:00+00:00

DB_DataObject Feature/Change Request
Reported by senna
2007-05-19T04:28:44+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
now, you cannot run createTables.php with PostgreSQL when you have defined any views in schema such as 'test_schema.test_view'.

so, I rewrote (Generate.php line220):
                // try getting a list of schema views first. (postgres)
                $views = $__DB->getListOf('schema.views');
                if (empty($views)|| is_a($views, 'PEAR_Error')) {
                    $views = $__DB->getListOf('views');
                }

Of cause, this does not work because PEAR_DB don't support 'schema.views'.
Now, I post a request to suport this.(Bug #11080: getListOf('schema.views'))

If my request is accepted in PEAR_DB, please accept this request :-)

DB_DataObject: Feature/Change Request 10858 [Open] joinAdd function

alexor_patator at yahoo dot fr — 2007-04-27T07:13:34+00:00

DB_DataObject Feature/Change Request
Reported by banquette
2007-04-27T05:32:46+00:00
PHP: 5.2.1 OS:  Package Version: 

Description:
------------
I d like to use the joinAdd method with a hard coded query like joinAdd("LEFt JOIN ..."); I did not find a way to pass throught a table ; i mean when a table is not directly "connected" to another.

Test script:
---------------
<-> means a relationship between table (FK/PK)

table0 <-> table1 <-> table2 <-> table3
One can query table1 with a joinAdd on table0 and/or table2 but not with a joinAdd on table3 as there is no direct relationship. To do such a thing query must actually be hard coded... or I did not find the solution ...
That s why I want a "joinAdd(string $join)" : to keep advantage of methods like selectAdd() to avoid a hard coded query.

Thanks.

DB_DataObject: Bug 10326 [Open] Update on record using update($orignal) method with null values inserts 0's

pear at spinink dot net — 2008-03-23T05:33:06+00:00

DB_DataObject Bug
Reported by spin
2007-03-10T20:25:15+00:00
PHP: 5.2.0 OS: Linux Package Version: 1.8.5

Description:
------------
I've done a get(), the get returns null values for the fields in question. after doing the get, I do not change any values in the form. I submit a form to edit a record in the DB. The database table has several fields that allow NULL values. the update is of the following form.

$object->update($original)

This bug has been reported before and is still a problem here using mysql.

https://pear.php.net/bugs/bug.php?id=4919&edit=2

Test script:
---------------
I'm sorry but i do not have the skills needed to make a simple test case, I am instead posting debug output from DBDO that shows the state of the original object and the object to be updated and that they are identical with null values in place.
$DO_ORIGINAL===========DO_TblProperties Object
(   [__table] => tblProperties
    [intPropertyID] => 3
    [decSqFt] => 
    [intHalfBaths] => 
    [intDeposit] => 
    [intPriceFurnished] => 
    [intLeaseLength] => 
$DO_RENTALS===========DO_TblProperties Object
(   [__table] => tblProperties
    [intPropertyID] => 3
    [decSqFt] => 
    [intHalfBaths] => 
    [intDeposit] => 
    [intPriceFurnished] => 
    [intLeaseLength] => 

Expected result:
----------------
I expect that the DB record would not be updated since the original object and the object to update are identical and have empty values(null) that are allowed to be null in the DB.

Actual result:
--------------
DO_TblProperties   : QUERY       : UPDATE  `tblProperties`  SET `decSqFt` = 0 , `intHalfBaths` = 0 , `intDeposit` = 0 , `intPriceFurnished` = 0 , `intLeaseLength` = 0   WHERE (  `tblProperties`.`intPropertyID` = 3 )

DB_DataObject: Feature/Change Request 9949 [Verified] Transaction support

2008-06-29T04:47:40+00:00

DB_DataObject Feature/Change Request
Reported by doctor@...
2007-01-25T15:28:44+00:00
PHP: Irrelevant OS: Irrelevant Package Version: 1.8.5

Description:
------------
Is it possible/reasonable to implement transactions support into DataObject instance ? Maybe something like startTransaction() endTransaction() methods ?

DB_DataObject: Feature/Change Request 9910 [Analyzed] Custom connection support

soso_pub at yahoo dot com — 2007-03-06T22:34:51+00:00

DB_DataObject Feature/Change Request
Reported by soso_pub@...
2007-01-22T06:42:59+00:00
PHP: 5.0.0 OS: Any Package Version: 1.8.5

Description:
------------
It would be great that db objects can be set to use a custom db connection. This feature would solve a lot of problems regarding transactions because it adds the possibility to modify multiple db objects inside the same transaction - through the same connection.

DB_DataObject: Documentation Problem 9793 [Open] Documentation for Generator missing

powtac at gmx dot de — 2007-01-10T07:41:04+00:00

DB_DataObject Documentation Problem
Reported by powtac@...
2007-01-10T07:41:04+00:00
PHP: Irrelevant OS: Irrelevant Package Version: 1.8.5

Description:
------------
A documentation for the great feature of the generator is missing.


Somethinge like this:

require_once 'your config file';

require_once 'DB/DataObject.php';
require_once 'DB/DataObject/Generator.php';

DB_DataObject::debugLevel(5);

$generator = new DB_DataObject_Generator;
$generator->start();

DB_DataObject: Feature/Change Request 9389 [Open] JoinAdd / SelectAs overwriting each other

Bill at Explosivo dot com — 2006-11-20T21:29:46+00:00

DB_DataObject Feature/Change Request
Reported by Bill@...
2006-11-19T17:36:27+00:00
PHP: 4.3.10 OS: Linux / Windows Package Version: 1.8.4

Description:
------------
When I joinAdd two tables, and use selectAs to keep the fields from one from clashing with the other, they simply overwrite the contents of the first field.

$BUSINESS = DB_DataObject::factory("Business");
$BUSINESS->setId($buid);
$PERSON = DB_DataObject::factory("Person");
$BUSINESS->joinadd($PERSON);
$BUSINESS->selectAs($PERSON,'person_%s');

With this example, if I have:
BUSINESS.CITY = "BC"
PERSON.CITY = "PC"

I will get results containing:

CITY= "PC"
person_city = "PC"

My Query runs like:
QUERY: SELECT *, `person`.`id` as `person_id` , `person`.`firstname` as `person_firstname` , `person`.`lastname` as `person_lastname` , `person`.`address1` as `person_address1` , `person`.`address2` as `person_address2` , `person`.`city` as `person_city` , `person`.`state` as `person_state` , `person`.`zipcode` as `person_zipcode` , `person`.`latitude` as `person_latitude` , `person`.`longitude` as `person_longitude` , `person`.`gcscore` as `person_gcscore` , `person`.`contactphone` as `person_contactphone` , `person`.`birthdate` as `person_birthdate` , `person`.`role` as `person_role` , `person`.`activeind` as `person_activeind` , `person`.`email` as `person_email` , `person`.`updatedate` as `person_updatedate` , `person`.`accessdate` as `person_accessdate` , `person`.`passwordx` as `person_passwordx` , `person`.`passphrase` as `person_passphrase`
FROM `business`
INNER JOIN `findwellnesspros`.`person` ON `findwellnesspros`.`person`.`id`=`business`.`customerid`
WHERE ( `business`.`id` = 77590 )

Which if I cut it out and run it manually returns the data correctly (appears so).

Anyway, this comes back from debug level 5

dataobjects_business: RESULT: O:9:"db_result":11:{s:8:"autofree";b:0;s:3:"dbh";O:8:"db_mysql":8:{s:10:"autocommit";b:1;s:8:"dbsyntax";s:5:"mysql";s:3:"dsn";a:9:{s:7:"phptype";s:5:"mysql";s:8:"dbsyntax";s:5:"mysql";s:8:"username";s:8:"fwpuser1";s:8:"password";s:13:"working101dog";s:8:"protocol";s:3:"tcp";s:8:"hostspec";s:9:"localhost";s:4:"port";b:0;s:6:"socket";b:0;s:8:"database";s:16:"findwellnesspros";}s:8:"features";a:7:{s:5:"limit";s:5:"alter";s:8:"new_link";s:5:"4.2.0";s:7:"numrows";b:1;s:8:"pconnect";b:1;s:7:"prepare";b:0;s:3:"ssl";b:0;s:12:"transactions";b:1;}s:9:"fetchmode";i:1;s:22:"fetchmode_object_class";s:8:"stdClass";s:7:"options";a:8:{s:16:"result_buffering";i:500;s:10:"persistent";b:0;s:3:"ssl";b:0;s:5:"debug";i:0;s:14:"seqname_format";s:6:"%s_seq";s:8:"autofree";b:0;s:11:"portability";i:0;s:8:"optimize";s:11:"performance";}s:13:"was_connected";b:1;}s:9:"fetchmode";i:1;s:22:"fetchmode_object_class";s:8:"stdClass";s:11:"limit_count";N;s:10:"limit_from";N;s:10:"parameters";a:0:{}s:5:"query";s:1045:"SELECT *, `person`.`id` as `person_id` , `person`.`firstname` as `person_firstname` , `person`.`lastname` as `person_lastname` , `person`.`address1` as `person_address1` , `person`.`address2` as `person_address2` , `person`.`city` as `person_city` , `person`.`state` as `person_state` , `person`.`zipcode` as `person_zipcode` , `person`.`latitude` as `person_latitude` , `person`.`longitude` as `person_longitude` , `person`.`gcscore` as `person_gcscore` , `person`.`contactphone` as `person_contactphone` , `person`.`birthdate` as `person_birthdate` , `person`.`role` as `person_role` , `person`.`activeind` as `person_activeind` , `person`.`email` as `person_email` , `person`.`updatedate` as `person_updatedate` , `person`.`accessdate` as `person_accessdate` , `person`.`passwordx` as `person_passwordx` , `person`.`passphrase` as `person_passphrase`
FROM `business` INNER JOIN `findwellnesspros`.`person` ON `findwellnesspros`.`person`.`id`=`business`.`customerid`
WHERE ( `business`.`id` = 77590) ";s:6:"result";i:0;s:11:"row_counter";N;s:9:"statement";N;}


Then when I try to get the data:

dataobjects_business: FETCH: a:63:{s:2:"id";s:1:"2";s:10:"customerid";s:1:"2";s:4:"name";s:13:"My Big Muscle";s:9:"activeind";s:1:"0";s:5:"email";s:18:"bill@explosivo.com";s:10:"websiteurl";s:24:"http://www.explosivo.com";s:8:"address1";s:8:"74 UpUrs";s:8:"address2";s:0:"";s:4:"city";s:11:"New Britian";s:5:"state";s:2:"CT";s:7:"zipcode";s:5:"06489";s:8:"latitude";s:8:"0.000000";s:9:"longitude";s:8:"0.000000";s:7:"gcscore";s:1:"0";s:12:"contactphone";s:10:"8606215380";s:10:"contactfax";s:0:"";s:9:"photofile";s:0:"";s:10:"updatedate";N;s:15:"servicelocation";s:6:"office";s:10:"traveldist";s:1:"0";s:13:"referencesind";s:1:"0";s:12:"callbackdays";s:1:"0";s:11:"hoursmonbeg";s:1:"0";s:11:"hoursmonend";s:1:"0";s:11:"hourstuebeg";s:1:"0";s:11:"hourstueend";s:1:"0";s:11:"hourswedbeg";s:1:"0";s:11:"hourswedend";s:1:"0";s:11:"hoursthubeg";s:1:"0";s:11:"hoursthuend";s:1:"0";s:11:"hoursfribeg";s:1:"0";s:11:"hoursfriend";s:1:"0";s:11:"hourssatbeg";s:1:"0";s:11:"hourssatend";s:1:"0";s:11:"hourssunbeg";s:1:"0";s:11:"hourssunend";s:1:"0";s:9:"firstname";s:4:"Bill";s:8:"lastname";s:6:"Chmura";s:9:"birthdate";s:10:"1969-08-08";s:4:"role";s:13:"administrator";s:10:"accessdate";N;s:9:"passwordx";s:0:"";s:10:"passphrase";s:0:"";s:9:"person_id";s:1:"2";s:16:"person_firstname";s:4:"Bill";s:15:"person_lastname";s:6:"Chmura";s:15:"person_address1";s:8:"74 UpUrs";s:15:"person_address2";s:0:"";s:11:"person_city";s:11:"New Britian";s:12:"person_state";s:2:"CT";s:14:"person_zipcode";s:5:"06489";s:15:"person_latitude";s:8:"0.000000";s:16:"person_longitude";s:8:"0.000000";s:14:"person_gcscore";s:1:"0";s:19:"person_contactphone";s:10:"8606215380";s:16:"person_birthdate";s:10:"1969-08-08";s:11:"person_role";s:13:"administrator";s:16:"person_activeind";s:1:"0";s:12:"person_email";s:18:"bill@explosivo.com";s:17:"person_updatedate";N;s:17:"person_accessdate";N;s:16:"person_passwordx";s:0:"";s:17:"person_passphrase";s:0:"";}
dataobjects_business: fetchrow LINE: id = 2
dataobjects_business: fetchrow LINE: customerid = 2
dataobjects_business: fetchrow LINE: name = My Big Muscle
dataobjects_business: fetchrow LINE: activeind = 0
dataobjects_business: fetchrow LINE: email = bill@explosivo.com
dataobjects_business: fetchrow LINE: websiteurl = http://www.explosivo.com
dataobjects_business: fetchrow LINE: address1 = 74 UpUrs
dataobjects_business: fetchrow LINE: address2 =
dataobjects_business: fetchrow LINE: city = New Britian
dataobjects_business: fetchrow LINE: state = CT
dataobjects_business: fetchrow LINE: zipcode = 06489
dataobjects_business: fetchrow LINE: latitude = 0.000000
dataobjects_business: fetchrow LINE: longitude = 0.000000
dataobjects_business: fetchrow LINE: gcscore = 0
dataobjects_business: fetchrow LINE: contactphone = 8606215380
dataobjects_business: fetchrow LINE: contactfax =
dataobjects_business: fetchrow LINE: photofile =
dataobjects_business: fetchrow LINE: updatedate =
dataobjects_business: fetchrow LINE: servicelocation = office
dataobjects_business: fetchrow LINE: traveldist = 0
dataobjects_business: fetchrow LINE: referencesind = 0
dataobjects_business: fetchrow LINE: callbackdays = 0
dataobjects_business: fetchrow LINE: hoursmonbeg = 0
dataobjects_business: fetchrow LINE: hoursmonend = 0
dataobjects_business: fetchrow LINE: hourstuebeg = 0
dataobjects_business: fetchrow LINE: hourstueend = 0
dataobjects_business: fetchrow LINE: hourswedbeg = 0
dataobjects_business: fetchrow LINE: hourswedend = 0
dataobjects_business: fetchrow LINE: hoursthubeg = 0
dataobjects_business: fetchrow LINE: hoursthuend = 0
dataobjects_business: fetchrow LINE: hoursfribeg = 0
dataobjects_business: fetchrow LINE: hoursfriend = 0
dataobjects_business: fetchrow LINE: hourssatbeg = 0
dataobjects_business: fetchrow LINE: hourssatend = 0
dataobjects_business: fetchrow LINE: hourssunbeg = 0
dataobjects_business: fetchrow LINE: hourssunend = 0
dataobjects_business: fetchrow LINE: firstname = Bill
dataobjects_business: fetchrow LINE: lastname = Chmura
dataobjects_business: fetchrow LINE: birthdate = 1969-08-08
dataobjects_business: fetchrow LINE: role = administrator
dataobjects_business: fetchrow LINE: accessdate =
dataobjects_business: fetchrow LINE: passwordx =
dataobjects_business: fetchrow LINE: passphrase =
dataobjects_business: fetchrow LINE: person_id = 2
dataobjects_business: fetchrow LINE: person_firstname = Bill
dataobjects_business: fetchrow LINE: person_lastname = Chmura
dataobjects_business: fetchrow LINE: person_address1 = 74 UpUrs
dataobjects_business: fetchrow LINE: person_address2 =
dataobjects_business: fetchrow LINE: person_city = New Britian
dataobjects_business: fetchrow LINE: person_state = CT
dataobjects_business: fetchrow LINE: person_zipcode = 06489
dataobjects_business: fetchrow LINE: person_latitude = 0.000000
dataobjects_business: fetchrow LINE: person_longitude = 0.000000
dataobjects_business: fetchrow LINE: person_gcscore = 0
dataobjects_business: fetchrow LINE: person_contactphone = 8606215380
dataobjects_business: fetchrow LINE: person_birthdate = 1969-08-08
dataobjects_business: fetchrow LINE: person_role = administrator
dataobjects_business: fetchrow LINE: person_activeind = 0
dataobjects_business: fetchrow LINE: person_email = bill@explosivo.com
dataobjects_business: fetchrow LINE: person_updatedate =
dataobjects_business: fetchrow LINE: person_accessdate =
dataobjects_business: fetchrow LINE: person_passwordx =
dataobjects_business: fetchrow LINE: person_passphrase =
dataobjects_business: fetchrow: business DONE


The business city should be returned as southington.  

$BUSINESS = DB_DataObject::factory("Business");
$BUSINESS->setId($buid);
$PERSON = DB_DataObject::factory("Person");
$BUSINESS->joinadd($PERSON);
$BUSINESS->selectAs($PERSON,'person_%s');
$BUSINESS->selectAs($BUSINESS,'business_%s');

Now, if I do this... I get back the original data as shown above, the person table, and the business_ also.  The Person_ and the Business_ both show correct info, but the orignal business data fields are overwritten.

Anything I can do to help, or if you can tell me where to look at the code, or if I am an idiot...

let me know


Expected result:
----------------
SelectAs fields should not overwrite the default fields

DB_DataObject: Feature/Change Request 9076 [Open] Fetch a specific row

pas at pas dot net dot au — 2006-11-25T12:04:55+00:00

DB_DataObject Feature/Change Request
Reported by pas@...
2006-10-17T23:11:19+00:00
PHP: 5.1.6 OS: Debian Package Version: 

Description:
------------
How about changing the following in DataObject.php

function fetch($rownum = NULL)
...
$array = $result->fetchRow(DB_DATAOBJECT_FETCHMODE_ASSOC, $rownum);

That way you could get any row in the result instead of only the next row. It is already supported by the DB class, so it is a very simple and minor change.

DB_DataObject: Feature/Change Request 8092 [Open] The fourth parameter of joinAdd() (DB_DataObject)

carlosjordao at gmail dot com — 2006-09-28T00:18:34+00:00

DB_DataObject Feature/Change Request
Reported by carlosjordao@...
2006-06-30T09:22:11+00:00
PHP: 4.4.2 OS: Linux Package Version: 

Description:
------------
 The joinAdd() fourth parameter is used when we don't have an .links.ini, otherwise the DB_DataObject will complain about it.

I propose to change that behavior. This fourth parameter should mean the entire on clause, not only the field used to make the join.

This would be a kind of "force" condition. If you don't have a .links.ini, you would use this pamareter anyway, but you can't disable .links.ini and use the fourth parameter.

I had experimented this kind of need, once the expression I used in the "on condition" made a different result when it was in the "where" . In this case, I needed a "LEFT" join.

DB_DataObject: Feature/Change Request 7949 [Open] ability to select a schema with Generator

peter dot termaten at gmail dot com — 2006-06-20T12:44:04+00:00

DB_DataObject Feature/Change Request
Reported by peter.termaten@...
2006-06-20T12:44:04+00:00
PHP: Irrelevant OS: PostgreSQL Package Version: 1.8.4

Description:
------------
Hi,

Using the Generator when building classes from PostgreSQL I figured it would be handy to generate only tables from a particular schema.
This could be achieved in a similar way as selected particular tables, by adding a Configuration option like : 'include_schema_regex'.

'exclude_schema_regex' could add an exclusion of a schema

See code sammple below

Test script:
---------------
Adding the following to Generator.php, method _createTableList
directly after the logic for stripping the schema part from the table name would do the trick:

if (isset($options['include_schema_regex'] ) &&            !preg_match($options['include_schema_regex'],$bits[0])) {
                continue;
            }

DB_DataObject: Feature/Change Request 6555 [Open] Can't update register with id 0

vtamara at pasosdejesus dot org — 2006-01-23T00:10:00+00:00

DB_DataObject Feature/Change Request
Reported by vtamara@...
2006-01-22T22:51:37+00:00
PHP: Irrelevant OS: Any Package Version: 

Description:
------------
The function update (even in CVS) includes the following piece of code:

if (empty($this->{$keys[0]}) && $dataObject !== true) {
    $this->raiseError("update: trying to perform an update without 
         the key set, and argument to update is not 
         DB_DATAOBJECT_WHEREADD_ONLY
         ", DB_DATAOBJECT_ERROR_INVALIDARGS);
   return false;  
}

Since the empty function returns true when its argument is
0, the error is produced also when the key of the DataObject
is 0.

In my humble opinion the condition of the if should be:

if ($this->{$keys[0]}!=0 &&
   empty($this->{$keys[0]}) && $dataObject !== true) {

Am I right?

Best regards. Thanks for the good work.  God illuminate us.

DB_DataObject: Feature/Change Request 6202 [Open] getLinkArray() missing

nbraczek at bsds dot de — 2006-05-08T02:35:22+00:00

DB_DataObject Feature/Change Request
Reported by nbraczek@...
2005-12-08T23:25:58+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
The quite usefull method getLinkArray() is not mentioned in the documentation. It is found in DB_DataObject 1.7.15 with a wrong/misleading description.

The doc entry should look like this:

(see 'Test script' field)

regards,
Niels Braczek 

Test script:
---------------
-> getLinkArray()
-> getLinkArray() -- fetch and return a list of related objects

Synopsis
mixed $DB_DataObject->getLink (string $column [, string $table])

Description
Fetch an array of related objects. This should be used in conjunction with a .links.ini file configuration (see the introduction on linking for details on this).
You may also use this with all parameters to specify, the column and related table.

Parameter
* string $column - either column or column.xxxxx
* string $table - name of table to look up value in

Return value
array - array of results (empty array on failure)

Note
This function can not be called statically.

Example
Example xx-1. Getting the related objects

get(12);
$children = $person->getLinkArray('children');

echo 'There are ', count($children), ' descendant(s):
';
foreach ($children as $child) {
    echo $child->name, '
';
}
?>

DB_DataObject: Feature/Change Request 5997 [Open] getlinks on multible column keys

2006-03-07T12:13:42+00:00

DB_DataObject Feature/Change Request
Reported by nikolas.hagelstein@...
2005-11-17T08:14:37+00:00
PHP: Irrelevant OS: Linux 2.4.30 Package Version: 

Description:
------------
AFAIK it,s not possible to use getLinks() in common with multible column links.

e.g.:

3 DB-tables

--------
|person| Primary key on two colums (id and f_id)
--------
|id    |
--------
|f_id  |
--------

------
|firm|
------
|id  |
------

------
|car |  Car belongs to a person which belongs to a firm
------
|p_id|
|----|
|f_id|
------

So getlinks isn't able to fecht a cars corresponding person.

DB_DataObject: Feature/Change Request 5790 [Open] Automatically determine insert/update for an object

richtl at arscognita dot com — 2005-10-27T20:15:38+00:00

DB_DataObject Feature/Change Request
Reported by richtl@...
2005-10-26T11:17:36+00:00
PHP: 5.1.0 OS: Linux Package Version: 

Description:
------------
The MyObjects library has a store() function that automatically determines whether an object should be inserted or updated depending on whether it exists in the database.

I find I'm writing a log of "if this->find() then update else insert" sorts of structures. It would make sense to move this into the DB_DataObjects code.

What I'm proposing is essentially,

function store() {
  if( object exists in the database ) {
    // update it from object properties
  } else {
    // insert it as a new row
  }
}

DB_DataObject: Feature/Change Request 4713 [Verified] builde sql use prepare feature

kenchou77 at gmail dot com — 2005-06-30T01:09:44+00:00

DB_DataObject Feature/Change Request
Reported by kenchou77@...
2005-06-29T21:34:26+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
prepare & execute sql(like PEAR DB Package)

Reproduce code:
---------------
require_once 'DB/DataObject.php';

$config = parse_ini_file('../example.ini',TRUE);
foreach($config as $class=>$values) {
	$options = &PEAR::getStaticProperty($class,'options');
	$options = $values;
}

$sell = DB_DataObject::factory("SELL_TABLE");

$sell->whereAdd('dele = 0');
$sell->orderBy('ID DESC');
$sell->limit(0,20);

$count = $sell->find();


Expected result:
----------------
debug output:
QUERY: SELECT ... FROM (SELECT rownum as linenum, ... FROM (SELECT * FROM SELL_TABLE WHERE dele = 0 ORDER BY ID DESC ) WHERE rownum <= 20) WHERE linenum >= 1

Actual result:
--------------
for Oracle(and other db supported):
QUERY: SELECT ... FROM (SELECT rownum as linenum, ... FROM (SELECT * FROM SELL_TABLE WHERE dele = ? ORDER BY ID DESC ) WHERE rownum <= ?) WHERE linenum >= ?

DB_DataObject: Feature/Change Request 4306 [Verified] No way to specify logic condition in nested joinAdd and whereAdd

2005-05-17T18:17:41+00:00

DB_DataObject Feature/Change Request
Reported by ej.grace@...
2005-05-09T10:11:01+00:00
PHP: 4.3.10 OS: Linux Package Version: 

Description:
------------
When combining joinAdd and whereAdd conditions the whereAdd conditions on the seperate objects are combined implicitly with AND in the generated SQL.  

For example 

$country->whereAdd('name = \'Germany\'');
$person->joinAdd($country);
$institution->whereAdd('name = \'test\'');
$person->joinAdd($institution);
$person->fetch();

Combines the condition on $country and $institution with 'AND' so that it would fetch people where their names are 'test' AND they are in a country with the name 'Germany'

Reproduce code:
---------------
The following diff adds an optional joinAdd logic parameter which is passed through to the subsequent whereAdd calls.

This allows one to carry out the join add mentioned above returning records with 'Germany' as the name in the country table OR 'test' as the name of the institution.

18c18
<  * @version    CVS: $Id: DataObject.php,v patch 2005/05/09 16:02:00 graceej Exp $
---
>  * @version    CVS: $Id: DataObject.php,v 1.353 2005/04/20 07:50:01 alan_k Exp $
2822,2824d2821
<      * @param    optional $joinLogic string     The whereAdd logic to use when adding whereAdd conditions
<      *                                          to nested joins default is 'OR' (default is 'AND')
<      *
2829c2826
<     function joinAdd($obj = false, $joinType='INNER', $joinAs=false, $joinCol=false, $joinLogic='AND')
---
>     function joinAdd($obj = false, $joinType='INNER', $joinAs=false, $joinCol=false)
2836d2832
<
3016c3012
<                 $this->whereAdd("{$joinAs}.{$ofield}={$table}.{$tfield}",$joinLogic);
---
>                 $this->whereAdd("{$joinAs}.{$ofield}={$table}.{$tfield}");
3055c3051
<                     )),$joinLogic);
---
>                     )));
3059c3055
<                 $this->whereAdd("{$joinAs}.{$kSql} = {$obj->$k}",$joinLogic);
---
>                 $this->whereAdd("{$joinAs}.{$kSql} = {$obj->$k}");
3063c3059
<             $this->whereAdd("{$joinAs}.{$kSql} = 0",$joinLogic);
---
>             $this->whereAdd("{$joinAs}.{$kSql} = 0");
3078c3074
<         $this->whereAdd("($cond)",$joinLogic);
---
>         $this->whereAdd("($cond)");

DB_DataObject: Feature/Change Request 3773 [Verified] Re: [PEAR-BUG] Bug #3773 [Ctl->Fbk]: PostgreSQL SERIAL type not supported

2006-10-15T21:12:46+00:00

DB_DataObject Feature/Change Request
Reported by ej.grace@...
2005-03-11T08:24:37+00:00
PHP: 4.3.10 OS: Linux Package Version: 

Description:
------------
[PREFIX]
This appears to have been mentioned in bug #57 Auto Sequence problem with PostgreSQL.  This bug report does however contain a workaround which may be useful.


There appears to be a bug in DB::DataObject which causes the autoincrement of primary keys to use a different table to the default table created by PostgreSQL when specifying the SERIAL type.

I suspect that the function ->keys(), ->sequenceKey() et al.  does not return the correct name of the primary key. For this reason the internal bits of DB::DataObject determine the sequence table to be [TABLENAME]_seq rather than the PostgreSQL default [TABLENAME]_[KEYNAME]_seq.

This results in TWO sequence tables, one that is consulted when doing an explicit INSERT query, the other when using the ->insert() member function.

Needless to say these can (and do) clash.

The workaround is as follows:

Instead of using SERIAL, which implies 

colname integer DEFAULT nextval('tablename_colname_seq') NOT NULL

Specify the key as:

id BIGINT DEFAULT nextval('idclash_seq') NOT NULL

This will mean ->insert() and the pgsql INSERT command will use the same sequence key table.

Reproduce code:
---------------
Starting from a blank database:

CREATE TABLE idclash (
  id SERIAL,
  PRIMARY KEY id
);

Then at the psql command line do:

INSERT INTO idclash (id) VALUES (default);
INSERT INTO idclash (id) VALUES (default);

In a script call the insert member function:
->insert()
->insert()
->insert()

Finally at the psql command line do

INSERT INTO idclash (id) VALUES (default);
SELECT id FROM idclash;


Expected result:
----------------
id | 
----|
  1 |
  2 |
  3 |
  4 |
  5 |
  6 |
(6 rows)

Actual result:
--------------
id |
----
 1 |
 2 |
 3 |
(3 rows)