On Thu, Jan 23, 2014 at 7:46 PM, Michael Bayer mike...@zzzcomputing.com wrote:
On Jan 23, 2014, at 2:07 PM, Simon King si...@simonking.org.uk wrote:
That's fantastic, thanks so much. I feel bad that my silly use case
has caused so much work for you and grown the docs even more (perhaps
you
On Thu, Jan 23, 2014 at 1:45 AM, Michael Bayer mike...@zzzcomputing.com wrote:
On Jan 22, 2014, at 7:17 PM, Simon King si...@simonking.org.uk wrote:
I read the bit in the docs about non-primary mappers but was scared
off by the almost never needed warnings. Actually, for the purposes
I'm
On Jan 23, 2014, at 2:07 PM, Simon King si...@simonking.org.uk wrote:
That's fantastic, thanks so much. I feel bad that my silly use case
has caused so much work for you and grown the docs even more (perhaps
you need a separate Tricks for People who Should Know Better
section)
oh but this
Hi all,
I've been having a little trouble configuring a relationship between 2
mapped classes where the join condition pulls in another 2 tables. I
eventually got it working based on Mike's method one from
On Jan 22, 2014, at 11:54 AM, Simon King si...@simonking.org.uk wrote:
Hi all,
I've been having a little trouble configuring a relationship between 2
mapped classes where the join condition pulls in another 2 tables. I
eventually got it working based on Mike's method one from
On 22 Jan 2014, at 23:45, Michael Bayer mike...@zzzcomputing.com wrote:
On Jan 22, 2014, at 11:54 AM, Simon King si...@simonking.org.uk wrote:
Hi all,
I've been having a little trouble configuring a relationship between 2
mapped classes where the join condition pulls in another 2 tables.
On Jan 22, 2014, at 7:17 PM, Simon King si...@simonking.org.uk wrote:
I read the bit in the docs about non-primary mappers but was scared
off by the almost never needed warnings. Actually, for the purposes
I'm using it for, a completely separate class mapped to the select
would probably be
