Thanks everyone, i'm also thought that mapping in separate classes
will be the solution, I just wanted to be sure that ther is no other
way.
On Jan 6, 4:38 pm, Hudson Akridge wrote:
> > How can I define that the related column in the CUSTOMER table will be
> > CustomerTypeCode and not CustomerId?
My understanding is that this is fixed. I'm using an automapped base
class with a Version property and it works fine.
On Thu, Jan 7, 2010 at 7:51 AM, Jeff Doolittle wrote:
> Does anyone know if a fix for this if forthcoming?
>
> --Jeff
>
> On Nov 13 2009, 10:18 am, Billy wrote:
>> I agree with D
Does anyone know if a fix for this if forthcoming?
--Jeff
On Nov 13 2009, 10:18 am, Billy wrote:
> I agree with Deeksy. The version property from a superclass was
> mapping automatically previously. Seems to require a manual mapping
> now or it gets completely ignored.
>
> Billy
>
> On Nov 5,
One option is to manually perform this action during a delete process. I've
kind of dubbed this pattern the "Dereference Pattern". This gets fired
whenever an entity is deleted, and it raises events letting any associated
entities handle the entity deletion. In you other entities class, you can
sim
So far Fluent NHibernate is awesome and I'm progressively doing some
advance handling of tables with multiple relationships (reference
keys) with other tables. One scenario I'm figuring out is when I
delete an entity used (referenced) by "other entities", I want the
reference key column (property)
NHibernate is declarative, so your mapping is either a value or a reference
type as you're mapping it. Thus, I'm not sure I understand your point about
"inability to map lists of basic value types".
Now, if your'e talking about automatically guessing whether you're using a
or tag depending on yo
Tonya,
I can't give you an exact fix, because I use FNH Automapping, not
explicit map classes like you are using. But there seem to be many
similarities, and maybe the following will point you in a useful
direction.
I had to use an Automapping override. The syntax, tailored for your
example, wo
On Jan 5, 1:01 pm, Hudson Akridge wrote:
>
> Reason: By default collections are mapped to a reference type. If mapping to
> a value type (such as string) then you need to let NH know that it's an
> element, and not a class association.
Like Tonya and several others, I have also been tripped up
>
> How can I define that the related column in the CUSTOMER table will be
> CustomerTypeCode and not CustomerId? (if I can at all)
I don't believe you can. The table you're performing a join on uses the PK,
while the table you're joining to can be defined by a KeyColumn. Ref:
http://ayende.com/B
I can't find anything in the nhibernate documentation that indicates
how you would do this with the xml. You might be best served asking on
the nhusers list to determine the necessary xml so that we can then
help you map it with FNH.
On Wed, Jan 6, 2010 at 11:25 PM, Olga wrote:
> Hello,
>
> I hav
Hello,
I have two tables that I want to map to one class that will looks
like:
CUSTOMER_INFO_CLASS.cs
--
Id (CUSTOMER table)
CustomerName (CUSTOMER table)
CustomerTypeDesc (CUSTOMER_TYPE table)
I tried to do it with join, as follows:
Table("CUSTOMER");
Id(x => x.ID).Length(1
11 matches
Mail list logo
