Login | Register
My pages Projects Community openCollabNet

propel
Reply to message

* = Required fields
* Subject
* Body
Attachments
Send reply to
Topic
Author (directly in email)
Please type the letters in the image above.

Original message

Author Cameron Brunner <cameron.brunner@gmail.com>
Full name Cameron Brunner <cameron.brunner@gmail.com>
Date 2007-07-12 15:04:01 PDT
Message haha, always reread the diff before you send it... leftover methods
now removed. see how ya's like this version

On 7/13/07, Cameron Brunner <cameron.brunner@​gmail.com> wrote:
> 8am, time for work, untested but it should work... needs comments put
> back in it etc but i was mostly interested in getting this done for
> now.
>
> Enjoy!
>
> On 7/13/07, Cameron Brunner <cameron.brunner@​gmail.com> wrote:
> > Interest permits from me until i goto work this morning, playing now :)
> >
> > On 7/13/07, Hans Lellelid <hans at velum dot net> wrote:
> > > I'd add that perhaps what Oliver has written becomes the first version
> > > of DebugPropelPDO -- and we can add these new features in as time and
> > > interest permits.
> > >
> > > Hans
> > >
> > > Hans Lellelid wrote:
> > > > I think that's a very good suggestion.
> > > >
> > > > Hans
> > > >
> > > > Cameron Brunner wrote:
> > > >> I would be more interested at this point in offering DebugPropelPDO as
> > > >> a connection object type and adding a full array of debug info (query
> > > >> timing, counting, dupe query detection) to it and have a flag that
> > > >> switches to it when requested. Query timing generally interests me
> > > >> more than the count.
> > > >>
> > > >> Just my 2c
> > > >>
> > > >> On 7/13/07, Oliver Schonrock <oliver at realtsp dot com> wrote:
> > > >>> Hans Lellelid wrote:
> > > >>>> This looks interesting, Oliver. Other than not being able to use
> > > >>>> user-defined class with persistent connection (am I understanding that
> > > >>>> correctly? seems odd), were there any other limitations?
> > > >>>>
> > > >>> I checked what the story is with that "Cannot be used with persistent
> > > >>> PDO
> > > >>> instances.". It throws a PHP warning and behaves irractically. Suspect
> > > >>> it's kind of like unserializing a class from session without having the
> > > >>> class defined first. ie you get half an object.
> > > >>>
> > > >>> better patch takes care of the "Cannot be used with persistent PDO
> > > >>> instances." problem by checking the PDO config and refusing to subclass
> > > >>> PDOStatement. Consequently the getQueryCount() method doesn't work
> > > >>> correctly anymore and therefore throws an exception.
> > > >>>
> > > >>> this should ensure backward compatibility.
> > > >>>
> > > >>> http://propel.phpdb.​org/trac/ticket/454#​comment:2
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > > >
> > > > --------------------​--------------------​--------------------​---------
> > > > To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> > > > For additional commands, e-mail: dev-help at propel dot tigris dot org
> > > >
> > >
> > > --------------------​--------------------​--------------------​---------
> > > To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> > > For additional commands, e-mail: dev-help at propel dot tigris dot org
> > >
> > >
> >
> >
> > --
> > Cameron Brunner
> >
> > Want a better web browser?
> > http://www.spreadfir​efox.com/?q=affiliat​es&id=182780​&t=1
> >
>
>
> --
> Cameron Brunner
>
> Want a better web browser?
> http://www.spreadfir​efox.com/?q=affiliat​es&id=182780​&t=1
>
>


--
Cameron Brunner

Want a better web browser?
http://www.spreadfir​efox.com/?q=affiliat​es&id=182780​&t=1