I am using AutoMap exclusively as well (but am also very new at
this). I have gotten the Many-to-one mapping without changing
manyToOnePart.write.
in the parent class I have:
public virtual IList Children { get; set; }
in child class I have:
public virtual Parent Parent { get; set; }
parent xm
Text length not being set in schema. I am using AutoMap for my schema
and I added a convention to set the string length to 32. The exported
xml shows the correct mapping but the 'create table' query sent to db
(Access) does not contain the length number - just a $1 placeholder.
I do not know whe
It worked! Thanks a lot for the answer!!
Marcos Castilho da Costa Matos
--~--~-~--~~~---~--~~
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@googlegroups.
Usually this problem occurs because the session used to export the schema is
different to the session used to then query/execute against the db. The
problem with the sessions being different is that they don't share the same
underlying db connection, and you lose the changes made in the schema step
Hmm. For some reason I thought there was a fluent interface for defining
filters. Typically in this sort of scenario I use the google code search for
the xml element name such as "filter-def". In this case its turned up no
results so it seems that I was mistaken.
So what I suggest is that you defi
Well as I understand it, the problem is with using the persistence
specification to verify the mapping. The mapping itself works, its just the
the persistence specification isn't sophisticated enough to support the
testing of this scenario. Am I missing something?
On Sat, Apr 25, 2009 at 10:45 AM,
I use the following convention:
public class EnumConvention : IPropertyConvention
{
public bool Accept(IProperty target)
{
if( target.PropertyType.IsEnum )
{
return true;
}
Type t = Nullable.GetUnderlyingType(t
