[Deprecated] DMZ 1.5.3 (DataMapper OverZealous Edition)

[eluser]OverZealous[/eluser]
@mrtavo

Well, my guess is it is an issue between sqlite and CodeIgniter, as DataMapper doesn't write any raw SQL code, nor does it have any control over the output.

DataMapper does not really support dynamically created databases, so I am unable to provide further help for this problem at this time.

Please let me know if you discover a solution!


@mcnux
If the result of the save returns FALSE, this means one of two things:

1) The validation failed. This should always show an error unless you are using custom validation code.

2) The saving of a related object failed. There are a few common reasons for this:
• First, the related object being saved is not saved.
• Second, the object itself isn't saved (but this shouldn't ever happen).
• Third, the most often case, your relationship properties are not correctly configured. Please see the FAQs

To help alleviate this in the future, I'm adding code to DMZ 1.4 that will create error messages when a related save fails. For now, please carefully check your relationship configuration, and make sure that you do not have any typos on either side of the relationship.


@Daniel H
Those SELECT * FROM {table} WHERE {field}_id IS NULL queries are bugs. I found them recently during my testing, and have them fixed in the next release of DMZ (which is now 1.4.0). I didn't realize that it was also affecting the 'related_required' rules until you pointed it out.


The 1.4 release has a lot of fixes and improvements, but I'm still testing the new version. The goal is to have a completely functional test site that I can use to verify changes against. I probably won't have the updated version out until later this week, as creating a test bed is taking far longer than I originally estimated.