Jon Palmer [EMAIL PROTECTED] writes:
As I described in an earlier email, it's entirely right, indeed
preferable, that NHibernate does not add the where clause when you
query for the base class (as is always the case if there is only one
class).
It depends on your viewpoint. You are right
OK, I get it now.
I just thought about this solution below. It would save us from
creating a new project.
using System.Reflection;
...
protected override void InitializeParameter(IDbDataParameter dbParam,
string name, SqlType sqlType)
{
base.InitializeParameter( dbParam, name, sqlType
I think that a cleaner solution would be a separate project, but that would
work as well.
Can you create a patch for those?
On Sun, Sep 28, 2008 at 1:15 PM, Artur Dorochowicz
[EMAIL PROTECTED] wrote:
OK, I get it now.
I just thought about this solution below. It would save us from
creating
Patch is here:
http://sites.google.com/a/dorochowicz.com/artur-public-files/files-1/SqlServerCeDriver.cs.patch
That's against the trunk.
That should close this issue, I think. Thanks for your help Ayende.
On 28 Wrz, 13:19, Ayende Rahien [EMAIL PROTECTED] wrote:
I think that a cleaner solution
Thank you Ayende.
On Sep 25, 10:44 pm, Ayende Rahien [EMAIL PROTECTED] wrote:
Sigh,
I fixed the tuple stuff a week ago, not the list :-(
Yes, this is a bug.
Fixed.
I am currently running all the tests and will commit it shortly
On Wed, Sep 24, 2008 at 5:21 AM, Neal Blomfield [EMAIL
