Tag: Rdo
-
Rdo: Persistence is not your model
Remember that post on how your backend might betray you? You can store your Turba addressbook into an LDAP tree, but if the addressbook is manipulated from LDAP side, your CardDAV Sync may be ignorant of this. The bottom line is: You cannot trust the backend. Nor should the persistence model govern your application internal…
-
Horde/Rdo ORM: PSR-4 and BC Breaks
Summary: Horde/Rdo ORM got upgraded for Namespaces. User code conversion is straight-forward. Backward Compatibility is limited. If you ever wondered, RDO stands for Rampage Data Objects. This has been on my list for quite long, but it took some time to get it right. The horde/rdo library is horde’s Object Relational Mapping (ORM) solution. It…
-
Horde_Rdo Many to Many relations and Horde DB Migrator
Many to Many relations btween to object types or table rows are usually saved to a database using a third table. For example, if every server can have multiple services and each service can run on multiple computers, we need a third table to store the relations: server table: server_id | server_name 1 | hoellenhund.internal.company.com…
-
Horde 5 Preview: Sesha Inventory App 1.0 and updated Rdo library
Dear folks, I am very pleased to announce: The Sesha Inventory application is ready for Horde 5 and it is in good shape. Sesha is a simple inventory keeping application which originally developed by Bo Daley and Andrew Coleman on Horde 3. The product was never officially released but it went into production at several…