…a fails when including a behavior like `<behavior name="auto_add_pk" />`.
This constant, generated by `PHP5PeerBuilder::addConstantsAndAttribute()`, is no longer in use now that autoloading works for models. Besides, it creates problems (see #183) and complexity in the code. Removing it is painless - all the tests are green.
When using a join() (or a useXXXQuery()) on a query, and then terminating with findOneOrCreate(), Propel used to throw a non-explicit exception only in the case where there was no result found: PropelException: 'author.FIRST_NAME' could not be found in the field names of type 'colName'. These are: Array ... The problem is that Propel cannot set the foreign key value, as the main query uses a join and not a subquery. So Propel *should* indeed throw an exception, but it should explain what to do more clearly: PropelException: findOneOrCreate() cannot be used on a query with a join, because Propel cannot transform a SQL JOIN into a subquery. You should split the query in two queries to avoid joins. This exception is now also thrown when the query has a result, to help spot the problem during development (and not in production). Fixes #261.
that when dealing with object/array columns, the _unserialized fields will be cleared as well. Bug related tests: GeneratedObjectArrayColumnTypeTest:: testGetterDoesNotKeepValueBetweenTwoHydrationsWhenUsingOnDemandFormatter GeneratedObjectArrayColumnTypeTest:: testGetterDoesNotKeepValueBetweenTwoHydrationsWhenUsingOnDemandFormatter
…ally indexed arrays after cast to objects cannot be accessed by numeric property.
reuse via the PropelOnDemandFormatter.