+1! very good. I need it
On Thu, Sep 4, 2008 at 6:04 AM, James Kovacs <[EMAIL PROTECTED]>wrote:
> The PersistenceSpecification requires that entities derive from
> FluentNHibernate.Framework.Entity base class and therefore have an Id
> property of type long. The submitted patch removes this requ
The PersistenceSpecification requires that entities derive from
FluentNHibernate.Framework.Entity base class and therefore have an Id
property of type long. The submitted patch removes this requirement allowing
PersistenceSpecification to be used with any PK name and type. Additionally
you can use
I have a class with binary array:
private readonly byte[] _data;
public byte[] Data
{
get { return _data; }
}
The basic mapping sets up a varbinary(8000). I'd like to use an image
column. My hbm mapping file would look like this:
I can't figure out a way to do this with the fluent d
I'd be very happy with my original patch being applied... i really
really really do dislike all those magic strings when we don't need
them anymore.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Fluent NHibernate"
I've just applied your patch, enjoy.
On Wed, Sep 3, 2008 at 2:27 AM, Derick Bailey <[EMAIL PROTECTED]>wrote:
>
> i submitted a patch for this a while back, but it was never applied.
> you can get it here:
>
> http://code.google.com/p/fluent-nhibernate/issues/detail?id=31
>
>
> >
>
--~--~
Yeah soz, had some projects to finish off. Also I forgot all about the
issues list I'll spend some more time looking over it as well.
Cheers
Andy
On Wed, Sep 3, 2008 at 6:06 PM, James Gregory <[EMAIL PROTECTED]>wrote:
> I'll take a look sometime between now and friday. As with Chad, life
> happ
I am sorry as well right now, I am in the process of switching jobs and life
is a bit crazy right now.
On Wed, Sep 3, 2008 at 11:33 AM, Andrew Stewart <
[EMAIL PROTECTED]> wrote:
> Yeah soz, had some projects to finish off. Also I forgot all about the
> issues list I'll spend some more time look
We've got an open issue on this. What's everybody's opinions?
Personally, I prefer the first example over the second. I'm not keen on the
whole "slap a load of extension methods on a sealed class" practice. I'm not
adverse to it being in the project though. We've said in the past that
although this
Sorry for not getting back to you sooner. You can do subclasses like the
following:
DiscriminateSubClassesOnColumn("discriminatorColumnName")
.SubClass()
.IsIdentifiedBy("MySubclassDiscriminator")
.MapSubClassColumns(m =>
{
m.Map(x => x.MySubclassColumn;
});
The syntax
SetAttributeOnPropertyElement is on the PropertyMap class rather than
IProperty, although it probably should be pulled up.
On Wed, Sep 3, 2008 at 4:09 PM, Frank Bell <[EMAIL PROTECTED]> wrote:
>
> Hey,
>
> With regards to this, when checking the
> FluentNHibernate.Mapping.IProperty interface it d
I'll take a look sometime between now and friday. As with Chad, life
happens.
I have no intentions of letting this project stagnate, so don't worry about
that.
On Wed, Sep 3, 2008 at 2:17 PM, Chad Myers <[EMAIL PROTECTED]> wrote:
>
> Sorry man, I got blind-sided with life.
>
> We're about to make
Well I eventually got this to work by subclassing ClassMap to use
my own DiscriminatorPart and SubClassPart (based on the
Fluent NHibernate source), which I then hacked in the functionality
required. I doubt its the best approach, but at least I have it
working.
On Sep 1, 6:10 pm, Frank Bell <[EM
Hey,
With regards to this, when checking the
FluentNHibernate.Mapping.IProperty interface it does not contain a
definition for SetAttributeOnPropertyElement(). Am I missing
something?
Frank
--~--~-~--~~~---~--~~
You received this message because you are subscribed
Sorry man, I got blind-sided with life.
We're about to make the final switch at work from our old pre-FNHib
codebase to the FNHib trunk, so we should get suddenly more active.
I'll try to take these this weekend.
-c
-Original Message-
From: fluent-nhibernate@googlegroups.com
[mailto:[E
14 matches
Mail list logo
