[dev] Recent RDO changes

[Chuck Hagenbuch]

Quoting Michael Rubinsky <mike at theupstairsroom.com>:

> Alright, this is what I get for writing against HEAD code.  The  
> recent  commits regarding the new DML objects totally broke a bunch  
> of my  scripts.  While investigating the changes to the class  
> interfaces, it  seems like something like:
>
> <code>
> $results = $this->_flightMapper->storage()->getCursor($query);
> </code>
>
> would be the 'new' way of doing:
>
> <code>
>  list($sql, $bind) = $this->_flightMapper->storage()->process($query);
>  $results = $this->_flightMapper->storage()->query($sql, $bind);
> </code>

Yes. I have to say, though, that part of why I broke your code is I  
didn't know about your code. Meaning some of the RDO API changes are  
necessary and some things will keep evolving, but also I'm updating  
code that's in CVS throughout Horde or at least taking it into  
consideration.

Also I'm not really focused on using the storage drivers from outside  
of RDO, so feedback on how you want to do that - and discussion over  
whether that _should_ be catered to, I guess - would be welcome.

> from outside any of the RDO objects.  (Code in above example is from  
> a  storage driver for an app I'm working on, and obviously   
> $this->_flightMapper refers to a  private class instance of a mapper  
>  object which is set in the class' constructor).
>
> Running the above code causes my server to die with a segfault, no   
> other messages or log entries.

Ugh. :/

-chuck

-- 
"we are plastered to the windshield of the bus that is time." - Chris