well, so far this discussion has been about the community's (or at least a
loud subset) disagreement with Microsoft's take on the matter.
I'm not trying nor wanting to get into the middle of that.
People are starting an argument with me about my domain. A domain which
doesn't prevent me from accom
Well, it's an abstraction layer. It is supposed to separate your
domain from your database. Using NHibernate to put surrogate keys and
such into your domain objects, is perhaps a bit like using your iPhone
to hammer in a nail. Most people will probably not want to see
that. ;-)
On 7 Feb., 22:12, J
lol. i'd donate to the cause but i dont think it would make you think any
deeper than where you stopped, which was "boo your entity has a FK in it,
and even tho it shouldnt matter (and even tho NHib should be able to work
around it), i'm going to stop helping you because i dont like how you're
doin
i'm sorry, you got the attitude first.
non-answers, personal-opinion-first responses ... i didn't come here asking
to get into a jousting match about your preference, did i? I asked how i
would do something, given the expertise of the community.
--
You received this message because you are subsc
or, if what i'm trying to do won't work because NHib is getting confused
about a TicketID property on my domain with the same name as the TicketID
column in the database, you could suggest that I put another column on my
table that is GarbageColumnToEaseJamesMind and a property in my domain to
matc
How about dropping the attitude, and maybe I can help you? If not, you're on
your own. Fluent NHibernate is provided gratis, and support is provided out
of my own free time, if you're not happy with either you know the way out.
If you can't be civil, I'll go spend my time on other things more im
or you could answer all of my questions by prefacing your response with "If
you take the TicketID property out of your domain ... "
--
You received this message because you are subscribed to the Google Groups
"Fluent NHibernate" group.
To post to this group, send email to fluent-nhibernate@googl
OK fine.
forget my entity doesn't have another property which just happens to be a
FK.
wow magic! look it's gone! you don't have to be confused anymore.
Now ... how about answering all of the questions which don't have anything
to do with that?
Or if you need something easier, help me translate
I don't know. I've advised you not to put your foreign key ids in your
entities. If you insist on doing it, I'm afraid I can't help you.
--
You received this message because you are subscribed to the Google Groups
"Fluent NHibernate" group.
To post to this group, send email to fluent-nhibernate
"If you've got a foreign key id in your entity *you're doing it wrong*. It
really is as simple as that."
-- That's clearly a matter of opinion.
-- Is it a hack because I'm doing it backwards? Shouldn't I be able to:
References(x => x.Ticket).Column("TicketID").Not.LazyLoad()
Hi,
I wonder if there is any way to switch the default way that FNH runs
automappings.
Currently we use code similar to this:
foreach (BaseLibrary library in this.GetAllServerLibraries())
{
//mappings.UseOverridesFromAssembly(library.GetAssembly());
new
AutoMappingOverrideAlteration(libra
11 matches
Mail list logo
