Re: Postmodern changes affecting clsql-postgresql-socket3

That sounds like the appropriate action to take.  There are a few other 
outstanding patches as well that need to be rolled into an official 
release.  I think I should have time in the coming week or so to get 
that accomplished, though testing CLSQL is a bit of a bear.

Cheers, and thanks for pointing this out,
Russ Tyndall


On 8/17/2012 11:32 AM, Zach Beane wrote:
> cl-postgres now exports another symbol, POSTGRESQL-NOTIFICATION, related
> to the Postgres listen/notify mechanism. This causes a problem with
> clsql-postgres-socket, which uses POSTGRESQL-NOTIFICATION to name its
> own condition which has an incompatible superclass structure.
>
> It looks to me like cl-postgresql-socket3's package already shadows
> POSTGRESQL-WARNING. I think shadowing POSTGRESQL-NOTIFICATION would
> suffice to fix this new issue.
>
> What do you think?
>
> Thanks,
> Zach
> _______________________________________________
> CLSQL mailing list
> [email protected]
> http://lists.b9.com/cgi-bin/mailman/listinfo/clsql