Ok, no problem, you all do a great job!!
James Gregory schrieb:
> Time :)
>
> On 1/22/09, Stefan Lieser wrote:
>> There was a patch uploaded to support custom setter methods in
>> PersistenceSpecification. You need this if your domain model doesn't
>> have pub
y the patch or do you think it should not be applied for
other reasons?
Cheers
Stefan Lieser
--
http://clean-code-developer.de
http://nhplugin.lieser-online.de
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
&q
I've uploaded a patch to support specifying foreign key names on
ManyToMany like it was possible before for OneToMany.
See http://code.google.com/p/fluent-nhibernate/issues/detail?id=103
Cheers
Stefan Lieser
--
http://clean-code-developer.de
http://nhplugin.lieser-onli
> Reason? No one has grabbed the 2.0.1 binaries and put them in yet :)
I see... well we did it ;-)
> I'll see if I can get this in this weekend if possible, but no guarantees.
No problem.
Cheers
Stefan Lieser
--
http://clean-code-d
Hi Chad,
any reason for using 2.0 instead of 2.0.1?
Cheers,
Stefan Lieser
--
http://nhplugin.lieser-online.de
Chad Myers schrieb:
> FYI, there's a Rake target for switching the binaries. From the trunk/
> folder, type "rake -T".
>
> These tasks are of particular
supported yet, I hope I can fix that in the
next days.
Cheers,
Stefan Lieser
--
http://lieser-online.de
http://clean-code-developer.de
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Fluent NHibernate" g
Hi,
I've added support for one-to-one references (see attached patch).
In a ClassMap you can now write:
HasOne(x => x.Detail);
Cheers,
Stefan Lieser
--
http://nhplugin.lieser-online.de
--~--~-~--~~~---~--~~
You received this message because you are su
Hi,
I've added support for one-to-one references (see attached patch).
In a ClassMap you can now write:
HasOne(x => x.Detail);
Cheers,
Stefan Lieser
--
http://nhplugin.lieser-online.de
--~--~-~--~~~---~--~~
You received this message because you are su
second problem is with different databases. There will be an
MsSqlConnectionstring and a PostgreSqlConnectionString. To make this
"typesafe" we need special parameter types for the In(...) method.
So maybe its better to stick with the solution we just started?
Cheers,
Stefan Lieser
>
> You do the first on and I will add one for posttgresql
That's a word. Patch is attached.
Cheers,
Stefan Lieser
--
http://nhplugin.lieser-online.de
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
&q
eate
.ToProperties();
I've started to implement this and would contribute it as a patch.
Cheers,
Stefan Lieser
--
http://nhplugin.lieser-online.de
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Flu
11 matches
Mail list logo
