Validate() function that run as part of BuildMapping ?
On Sat, Jan 31, 2009 at 7:32 AM, Tuna Toksoz tehl...@gmail.com wrote:
For issue 2.
A Property/IValue needs some of(or many of) their props set, and yesterday
I forget to set one of the properties of SimpleValue namely Table, leading
to
Awesome.
On Mon, Jan 12, 2009 at 2:03 PM, James Gregory jagregory@gmail.comwrote:
As of last night there's a IdConvention where you should be able to do
what you need. Let me know if there's anything missing.
On 1/12/09, Ayende Rahien aye...@ayende.com wrote:
Is there a way to create
+1
That is what I seek
On Mon, Jan 12, 2009 at 2:36 PM, Chad Myers c...@chadmyers.com wrote:
[Credit to Aaron Jensen for giving some great feedback and sending me
down this thought path, and numerous others who have complained about lack
of private/protected member support and for
I have an entity that has a property called version, of type string.
FN tries to treat this as a version column, which fails. I think that the
version check should be on name + type, not just name.
--~--~-~--~~~---~--~~
You received this message because you are
int and long
On Sat, Jan 3, 2009 at 12:34 PM, James Gregory jagregory@gmail.comwrote:
That sounds reasonable, but which types should be treated as a version?
On Sat, Jan 3, 2009 at 9:25 AM, Ayende Rahien aye...@ayende.com wrote:
I have an entity that has a property called version
I think that I am missing something.
I have an entity that I want to map, and I want to be able to map it using
auto map, but be able to tweak some parameters. In this case, I just need to
set the length of one of the properties.
I think it should be possible without dropping out of auto mapping
what you can do is to interfer with the XML generation and work on that
On Thu, Dec 18, 2008 at 9:58 PM, Paul Batum paul.ba...@gmail.com wrote:
Chris I don't think you are missing anything. As far as I can tell
specifying the column ordering is not supported.
On Mon, Dec 15, 2008 at 4:56
are available if needed.
Thanks,
Jereme
On Dec 11, 2:05 pm, Ayende Rahien aye...@ayende.com wrote:
You can assume that I am going to do more there
On Thu, Dec 11, 2008 at 11:56 PM, Andrew Stewart
andrew.stew...@i-nnovate.net wrote:
Hi Oren
Glad you like the AutoMapping
Sorry to jump in the middle, but what exactly is the problem?
On Fri, Dec 12, 2008 at 9:25 AM, Paul Batum paul.ba...@gmail.com wrote:
Fair enough. What if the AutoPersistenceModel simply initializes the
Convention to use declaring/reflected type?
On Sat, Dec 13, 2008 at 12:25 AM, Chris
Trying out NH Prof with fluent nhibernate gave me a heart attack today, as I
saw a single statement translate into _many_ queries.Leaving aside the fact
that I was very happy to find that NH Prof can detect that, I traced that
down to DefaultLazyLoad being false by default.
This is the wrong
they are
most appreciated. I've applied your patch now.
Andy
On Thu, Dec 11, 2008 at 5:57 PM, Ayende Rahien aye...@ayende.com wrote:
Here is a patch to fix this issue.
On Thu, Dec 11, 2008 at 6:13 PM, Ayende Rahien aye...@ayende.com wrote:
It doesn't :-(It needs a global view of things to make
I think that there is a misunderstanding going on.Assuming that I
can reinterpret what Fabio has said.
1) Changes to the core of NH should be taken carefully.
2) Any such change should also include the ability to extend the default
mapping (which is going to be XML, unless things _drastically_
is not easy because:
- ORM have many options
- NH have tons of options
In this moment I don't have time to start ORuM... the real problem to
write a new mapping source, avoiding XML, is: have time to do it.
(well I know... the time is necessary but is not enough).
On 13 nov, 10:11, Ayende Rahien
One of the reasons NOT to use XML is performance.NH has to do schema
validation on the XML, and that is EXPENSIVE!
On Thu, Nov 13, 2008 at 3:13 PM, Paul Batum [EMAIL PROTECTED] wrote:
Well the point I was eluding to is that there might be a better way for us
to approach our implementation and
14 matches
Mail list logo
