Jim Tanner dobr...@gmail.com writes:
@Every one who might be interrested : This article deals with a way to
handle lazy loading in winforms.
http://www.codeproject.com/KB/cs/NHibernateLazyInitializer.aspx
I don't think this is a good idea, because it may lead to quite bad
performance. A much
ChrisHolmes cb.hol...@gmail.com writes:
I have yet to see anyone explain this clearly.
Ok, I'll try to give at least some guideline.
First of all: The most important thing to remember is that an ISession
is really unstable and unreliable (according to the book 'Exceptional
C++' of Herb Sutter
F.B. ten Kate folk...@bluenode.nl writes:
[session vs. stateless session]
Well wouldn't NHibernate be slow _every_ time i run this query then?
Not necessarily. I don't know the exact overhead, but the default,
stateful session uses caching mechanisms, so maybe filling the cache
is slow.
I
mhanney mrh5...@gmail.com writes:
regarding - All users of Oracle have a default schema that is
different than the schema where the tables live so all objects have to
be fully qualified with the schema name, you could use public
synonyms in Oracle:
CREATE OR REPLACE PUBLIC SYNONYM
Tyler Burd tb...@cudc.org writes:
Then you could have an NAnt target that would set up brail or some
other templating language, process the mapping files, and copy them
to a known directory.
Does that make sense?
Thank you very much, that makes perfectly sense. I already utilise
NAnt in
Fabio Maulo fabioma...@gmail.com writes:
the default_schema/default_catalog, of each mapping or of the
session-factory-configuration does not work ?
It does not work for the SQL in the 'formula' attribute of a property
(at least it didn't seem to work in 2.0.1GA last time I tried this).
--
Hi.
My database schema has quite some references and in order to avoid
loading always a great part of the wohle object graph I would like to
get some of the often used detail data directly in the entity without
denormalizing the schema.
Two concrete examples: In the following mappings the class
Hi.
I'm looking for best practices to sync multiple clients. In my domain
I have some bigger changes (for example generating many new lines in a
couple of tables or changing a state (and a couple of other
properties) for many lines). In another scenario (not that important
for my current
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
The problem is the call to NHibernateUtil.Initialize does not appear
to do anyting.
Why do you think this? NHibernateUtil.Initialize works just fine (at
least for me). After you initiliazation loop, try adding something
like this:
MAMMON [EMAIL PROTECTED] writes:
So does NH really achieve Persistence Ignorance?
IMNSHO it's a dumb idea to try to make your business layer completly
persistence ingnorant (in the way you suggest), because there is some
persistence in the background and you are developing a complex
system.
Tapio Kulmala [EMAIL PROTECTED] writes:
You said that foo = null is always false
Yes, he said that, but he didn't mean it. :)
This whole thread is another example of why it's a big design fault to
ever include NULL into SQL. Three valued logic is just not for
everyone.
As the cited link said:
MAMMON [EMAIL PROTECTED] writes:
The problem with views like this is that they are read only.
Why? Do you know about triggers? That's the easiest and most
straightforward solution, I would think.
--
Until the next mail...,
Stefan.
pgpa9RNXw7jwM.pgp
Description: PGP signature
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
Fabio Maulo [EMAIL PROTECTED] writes:
2008/9/16 Stefan Nobis [EMAIL PROTECTED]
2. Manual additions (DEFAULTs, triggers,...)
I plan to write a tool to generate all (except 2.)
2 is part of 1a (database-object)
Nah, NHibernate doesn't support an easy way to make those RDBMS
dependent. I
14 matches
Mail list logo
