interesting ! that answers that question (i.e., the question above the assertion statement) changed it to a "continue" in rev 2072.however, your mapping isnt going to work with those textual columns anyway since it cant intelligently construct an aliased select from it, you have to say:s =
Heh, that was easy.
I'm curious now, though, why it can't find the primary key with the
revised select you gave. (Works fine when I manually tell the mapper
what to use.)
On 10/30/06, Michael Bayer [EMAIL PROTECTED] wrote:
interesting ! that answers that question (i.e., the question above
because the available columns of the selectable is always treated
based on the columns declared. the FROM/WHERE is like the backend
to the query and the column clauses are the public interface. heh.
On Oct 30, 2006, at 7:02 PM, Jonathan Ellis wrote:
Heh, that was easy.
I'm curious
