[dev] RDO describe() limitation

[Chuck Hagenbuch]

Quoting Duck <duck at obala.net>:

> Horde_RDO_Storage describe problem
>
> I was in the middle of extending the general save() method to update even all
> the relationships. But i get into a problem. describe() presumes that a
> column has an primary key composed by only column. But how to handle
> container whit now primary key or better those with primary keys consisted of
> few columns?

I'd say that RDO isn't really designed to handle those sorts of  
things. Unless we _really_, really need it for RDO to be useful for  
"most" general use cases - not every use case, that's not the point -  
I'd avoid it.

> Like this only if we can handle only tables with one column primary   
> key and of
> course only one2one relationships. For example DataTree is a situation like
> this. When the attribute table is an one2many relationship. We are unable to
> update the attributes in any case.

Not sure what you mean here. All of the relationship types work in RDO  
right now, with single-keys for tables, at least in basic scenarios.

-chuck

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