Piotras' blog: Archive
2005-09-01 - 2005-09-30
New operators for MidgardQueryBuilder
Posted on 2005-09-03 15:40:22 UTC.
IN, NOT LIKE
I added these new operators to MidgardQueryBuilder constraints.IN operator should be very usefull for functions or object methods which could replace old midgard xxx_in_tree functions.
Simple note and example is now available in Midgard wiki documentation.
What is very interesting I also found and resolved quite important QueryBuilder's bug. When SQL operator used with constraints was invalid, QB selected all records from object's table.
Additionally PHP's phpinfo function reports now MgdSchema technology used.
MgdSchema metadata , the very first view
Posted on 2005-09-24 13:35:10 UTC.
This is the very first view so do not expect fully usable MgdSchema objects' metadata :)
MgdSchema metadata require the biggest and very difficult database change if you look back for midgard database updates in a past. However we have now quite usable midgard-data with datagard tool , so such update is done by dg.
What properties you can find as metadata ones? Currently not much. Author, created date, approved date, etc etc.
Example from real php object is better :
midgard_article Object
(
[guid] => 4f47cf4279a0bdc500c03edc459d4654
[sitegroup] => 0
[metadata] => midgard_metadata Object
(
[creator] =>
[created] => 2003-01-16 14:22:19
[revisor] => f6b665f1984503790ed91f39b11b5392
[revised] => 2003-04-30 10:30:06
[revision] => 3
[locker] => f6b665f1984503790ed91f39b11b5392
[locked] => 0000-00-00 00:00:00
[approver] => f6b665f1984503790ed91f39b11b5392
[approved] => 0000-00-00 00:00:00
[author] => f6b665f1984503790ed91f39b11b5392
[owner] =>
)
You may notice guid property being set. All MgdSchema types use this property automagically now without any need to select it from repligard table. Well, I have some work to do anyway. I "only" need to set those metadata properties when object is created or updated ;)