In my case, I should maybe have mentioned that I was using 1.2 and Firebird 2 database.
The failure was a bit obscure and took me a while to figure out (I'm quite new to this). However, after I renamed my field from: followupdate to: followdate, everything was working. When I get chance, I'll change it back again and see more exactly where the error occurs. I didn't investigate much further at the time because I thought maybe it was just (another) stupid mistake on my part. However, thinking about it now, I sure that this must be a bug because there are so many SQL reserved words to avoid that this could be a major restriction for anyone naming their fields. On Nov 23, 2:37 am, Gwoo <[EMAIL PROTECTED]> wrote: > This seems like more of a bug to me. It is most likely a by product of > some pragmatic programming, and maybe could be refactored to allow for > more use cases. I am curious what caused the problem with > "followupdate". I can certianly see why Adrian had trouble, but even > in his case it should not matter unless he is passing > personalIdentifiers to the view, in which case Cake would try to > populate a select. > > I hope that Adrian will expand on his experience a little more than to > just saying there are a few hiccups. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
