Massimiliano >> Yes, the fields were originally defined as booleans.
Eventually I had to change them to integers, as advised by Gareth.
I'm a bit disappointed about this regression, but the most important
is to have my app running fine.
Thanks, guys.
On 18 mar, 14:50, Gareth McCumskey wrote:
> A
Alter your schema to change the type to INTEGER, rebuild the model, do
a "symfony cc", then use the queries to check for 1 or 0 but with no
quotes so:
$c->add(ShowPeer::IS_PUBLISHED,1);
instead of:
$c->add(ShowPeer::IS_PUBLISHED,'1');
On Thu, Mar 18, 2010 at 3:15 PM, Massimiliano Arione wrote:
Are those fields defined as boolean in your schema?
Anyway, if you put your code in the correct model class, it's not
overwritten at every generation.
cheers
Massimiliano
On 17 Mar, 14:18, SlimShaggy wrote:
> Hello all,
> I am currently migrating an app from Symphony 1.2 to 1.4
> I am using an s
On Wed, 17 Mar 2010, SlimShaggy wrote:
> Changed the query, not the model. I tried to rebuild it, thoug
> with no success :(
I noticed that some symfony plugins had modified their code because of
this change in Propel so I imagine it might be similar in your case.
--
--
If you want to
>
> Which that change, did you try rebuilding models before clearing cache?
>
Changed the query, not the model. I tried to rebuild it, thoug
with no success :(
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this mess
