> SELECT "Resp"."id" AS "Resp__id", "Resp"."first_name" AS > "Resp__first_name", "Resp"."last_name" AS "Resp__last_name", > "Resp"."company_id" AS "Resp__company_id", "Resp"."created" AS > "Resp__created", "Resp"."modified" AS "Resp__modified" FROM "workers" > AS "Resp" WHERE "Resp"."id" = DEFAULT > > The query fails because of the DEFAULT... It seems it is due to the > value function in DBO_postgres.php...
I too have encountered this problem with 1.1.7. A diff between 1.1.7 and trunk shows no changes to dbo_postgres.php - have you had any luck with this bug nate? DEFAULT is an interesting choice to use in the value function - is it even valid SQL? I can't think of any case where it is in a select query, but I'm far from an SQL expert. James --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
