Yes, recently someone submitted a patch that broke a bunch of things. It has already been reverted in the git repository, but I guess quicklisp picked up the broken version (since it seems to assume that repositories are never broken). Update from git, I guess.
On Thu, Jan 23, 2014 at 9:07 AM, Colin Carr <colinpc...@gmail.com> wrote: > is update-dao in postmodern broken? > the strings are not being quoted > Database error 42703: column "croatia" does not exist > QUERY: (SELECT * FROM country WHERE (name = Croatia)) From the html > quickstart > (let ((croatia (get-dao 'country "Croatia"))) > (setf (country-inhabitants croatia) 4500000) > (update-dao croatia)) > > On Jan 22, 2014, at 4:33 PM, Sabra Crolleton <sabra.crolle...@gmail.com> > wrote: > >> After a recent quicklisp update, suddenly update-dao throws syntax errors. >> Simplest example: >> >> (update-dao (get-dao 'topic 182)) >> >> throws the following error: >> >> Database error 42601: syntax error at or near "Border" >> QUERY: UPDATE topics SET name = Cross Border Transactions, comments = NULL, >> usergroup_id = 1, permission_id = 1, parenttopic_id = 0 WHERE (id = 182) >> [Condition of type CL-POSTGRES-ERROR:SYNTAX-ERROR-OR-ACCESS-VIOLATION] >> >> I haven't updated anything and having a hard time trying to figure out what >> is triggering the problem. Anyone else seeing this or just me? >> >> Any pointers would be appreciated. >> >> Sabra > >
