You're right when you say "i must have some other problem there". When I changed the tinyint to int, my update would finally take, but now I notice that if I try to udate the same record with a different value in the int field, the update again stops working. Maybe there's something about cache I should know about? This is very frustrating for me. What's the point of a framework that takes ten times longer to figure out than it does to just write your own code? No offense to those who are developing cakePHP -- it's a great piece of work. It's just sometimes so frustrating.
On Sep 13, 10:39 am, "euromark (munich)" <[email protected]> wrote: > save and savefield? > no way.. > i had millions of those working fine the past 6 months > > you must have some other problem there > just one toggle value like "active": tinyint(1) unsigned NOT NULL > default '0' > etc > > On 13 Sep., 06:15, awstar <[email protected]> wrote: > > > just a heads up, i've spent most of the day trying to get a simple > > save and savefield to work, only to find it doesn't of the mySQL table > > defines the field as tinyint. > > > Just thought you'd like to know. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
