I also have this trouble in 0.22 so I just avoid sqlliteral :(
On Dec 2, 9:40 pm, "Scott Graham" <[EMAIL PROTECTED]> wrote:
> Thanks for the quick response.
>
> I had (sort of) tried that. For anyone else looking for this, I think it's
> more to do with the interpolation than with whether it's query or update.
>
> For example:
>
> web.query("update mytbl set mydt=$mydt", vars=dict(mydt=web.SQLLiteral
> ("now()")))
>
> also doesn't work, but
>
> web.query("update mytbl set mydt=now()")
>
> does work.
>
> Perhaps I'll check out the bzr version.
>
> thanks,
> scott
>
> On Dec 2, 2007 8:28 PM, Anand Chitipothu <[EMAIL PROTECTED]> wrote:
>
>
>
> > On 03-Dec-07, at 9:34 AM, Scott Graham wrote:
>
> > > Hi
>
> > > I'm having trouble getting NOW() to work using web.db. In the
> > > following code, the sql that's printed out looks OK (I think?) but the
> > > database complains that the value is out of range. Below is test code
> > > and the output that I get. Something obvious/dumb that anyone can
> > > see??
>
> > Looks like there web.update and SQLLiteral doesn't well together. Use
> > web.query instead of update.
>
> > This is already discussed here.
>
> >http://groups.google.com/group/webpy/browse_thread/thread/46117769e83...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web.py" 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/webpy?hl=en
-~----------~----~----~----~------~----~------~--~---
