On Apr 2, 4:47 am, Chris Hallwright <[email protected]> wrote:
> So it's clearly something in the blog example different from the > weblocks-clsql-demo that's causing the problem with clsql back-ends. > This should help narrow the search considerably. I suggest enabling statement logging on your Postgres server and checking what exactly happens on an SQL level when the erroneous delete is launched. You can also compare the working gridedit from the demo with the erroneous simple-blog gridedit on an SQL level. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" 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/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
