Andreas Flack writes: Hi!
>> Try to print_r DBA object to see if all properties are correctly >> assigned. > > They all looked fine. The only thing I found strange is that there was a > property called "action" with an empty value. I don't have a property > with that name, so it must get added automatically somewhere. Yes, it's base midgard_object property. As well as guid and metadata for example. > By playing around a little, I now found the problem: One of the DBA > classes contained a private var. When I changed this to public, the > segfaults for both DBA classes went away (the other class is the child > of the one with the private var). Is that a bug or is it generally not > allowed to add private vars to a DBA class? MidCOM 2.8 is not pure PHP5 framework. It was only adopted to run with PHP5. The same midgard-php bindings. That's why I didn't renamed it to midgard-php5. I doubt it can be fixed in 1-8 branch. At least it should work perfectly with upcoming 1.9 release. Midgard-php5 there, is pure language bindings. Piotras _______________________________________________ user mailing list [email protected] http://lists.midgard-project.org/mailman/listinfo/user
