Dear Alain,
I think you have analyzed the problem very well. As you say, in the
postmodern codebase in the file query.lisp, the macro "doquery"
utilizes the *database* variable with no obvious way to override or
specify it. I would have to study some more to be absolutely sure,
but it does seem
AP> When I tried the above, it blew up when I added the
ENSURE-TRANSACTION
clause; because all of a sudden the DOQUERY found itself querying
on the "wrong" database. (I'm assuming ENSURE-TRANSACTION binds
something like a *DATABASE* var which got mistakenly inherited by
Dear Elephant developers,
I'm trying to develop an application using Elephant, and
I think I've settled on the POSTMODERN back end.
Now, part of the application maps very naturally in what Elephant can
do, and other parts of it map better onto raw SQL processing,
where I wish to use POSTMODERN m