> grigrim so you are saying that the model would unserialize the data on
> an afterFind function? Rather than me manually looping through and
> unserializing the data?
Well, yeah - manually looping through and whatnot is a pain. I'm just
never sure exactly what format the data is in in afterFind(
grigri, that m at the end of your name was supposed to be a comma. m
= , apparently
On May 2, 10:03 am, validkeys <[EMAIL PROTECTED]> wrote:
> grigrim so you are saying that the model would unserialize the data on
> an afterFind function? Rather than me manually looping through and
> unserializin
grigrim so you are saying that the model would unserialize the data on
an afterFind function? Rather than me manually looping through and
unserializing the data?
On May 2, 8:33 am, grigri <[EMAIL PROTECTED]> wrote:
> I was going for this approach on a project a while ago... didn't do it
> in the
I had run across an article a while ago talking about gzipping large
bodies of text before writing it to the database and wondered the same
sorts of things...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP"
I was going for this approach on a project a while ago... didn't do it
in the end though.
I'm sure that it's always possible to avoid having to do this, but in
some cases it might be well worth it.
There doesn't seem to be an easy, well-documented way of handling this
sort of thing. I mean, wher
I have an app which has 2 types of quote requests. Rather that have 2
seperate tables with tons of fields, I serialize all of the form data
and just store it in one field. Besides the obvious searching
downside, is there any practical or standards downside to what i am
doing?
I only ask because i
