[Tickets #8225] Re: Rdo Mapper update function cannot create new records from Horde_Rdo_Base objects

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/8225
------------------------------------------------------------------------------
  Ticket             | 8225
  Updated By         | tenorviol at yahoo.com
  Summary            | Rdo Mapper update function cannot create new records
                     | from Horde_Rdo_Base objects
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             |
------------------------------------------------------------------------------


tenorviol at yahoo.com (2009-04-28 00:42) wrote:

After poking around with this a bit more, I've realized that This only  
happens for MySQL tables that have not set their primary key field to  
auto_increment.  I'm still not convinced it's best form to dump an  
empty primary key down an insert statement, but MySQL does handle this  
gracefully when the table is an auto_increment table. I have not  
tested this on other database server types. Here is example SQL  
generated by Horde_Rdo_Adapter::create.

INSERT INTO `mytable` (`mytable_id`, `user_uid`, `title`,  
`description`, `created`, `updated`) VALUES (?, ?, ?, ?, ?, ?)

Values Array ( [0] => [1] => admin [2] => actually [3] => do it [4] =>  
1240893214 [5] => 1240893214 )