I believe that the problem is a property which has the same name in base
class.
i mean
A
{
Name
}
B:A
{
Name
}
Tuna Toksöz
Eternal sunshine of the open source mind.
http://devlicio.us/blogs/tuna_toksoz
http://tunatoksoz.com
http://twitter.com/tehlike
On Sun, Jul 26, 2009 at 2:58
Just to double-check, do you have .Net 2.0 SP1 installed? (i.e., all the
latest updates to the .Net framework?)
There used to be a bug in .Net2.0 that caused this. (but it's a while since
I've seen it tbh - just a wild stab in the dark)
Hi,
I've been trying to use a static proxy so that I can use NHibernate
with medium trust hosting. I'm able to generate the proxy class as per
the intructions (http://nhforge.org/wikis/howtonh/pre-generate-lazy-
loading-proxies.aspx) but am getting errors when I try to use them.
The error
Although you may have heard the news before this message arrives your email
box, I still want to announce the release of NHibernate.Linq
More info can be found at
http://nhforge.org/blogs/nhibernate/archive/2009/07/26/nhibernate-linq-1-0-ga-released.aspx
It was related to this:
//m.Map(
//Reveal.PropertyProvidedInsuranceCardData(
//providedMemberIdOfPatient),
// vc_MemberID);
m.Map(x = x.ProvidedMemberIdOfPatient,
vc_MemberID).Access.AsCamelCaseField();
I had to replace the commented stuff with the uncommented stuff. I
also
I did it like this (and it seems to work nicely):
var types =
assembly.GetTypes().Where(
t =
typeof(DomainObjectInt64).IsAssignableFrom(t)).ToList(); // well thats
_my_ marker
types.ForEach(t =
{
Hi there,
for my database-objects to work (full text initialization on mssql), I would
need to know the name of my primary keys.
unfortunately, I have no idea, how to set this value. Anyone can help me? I
could set this in code, too, does not have to be in the mapping.
Thanks,
--
Jan
AFAIK you can't set the primary key name. Foreign keys yes, primary no.
On Sun, Jul 26, 2009 at 8:49 PM, Jan Limpens jan.limp...@gmail.com wrote:
Hi there,
for my database-objects to work (full text initialization on mssql), I
would need to know the name of my primary keys.
unfortunately, I
First I love how easy it is to use FutureT but I think it's only
half baked. or put in another way only implemented for server side
code that is not returning a list.
I have this code that's is returning a lot of simple catalogs for
comboboxes
OperationContract]
public CatalogsForSite
how exactly do you expect a Future to work over a webservice with marshalling
in between? You should rethink your context boundaries - usually when crossing
an AppDomain boundary you should already have all data you need in place and
ready for marshalling them. Any form of lazy evaluation will
I am not new to NH or the way lazy load works.
I work in a group of 6 developers and we have been working since new
year with NH over WCF and Silverlight as the UI.
when I call var c = stypes.Any(); I can see from the unit test that NH
is calling the databasen and that I have the corect data in
it's indeed not a lazy loading issue... the problem is that the DataContract
has one or more properties that are defined as IEnumerableT, but the
DataContractSerializer will choke on that if those references are actually
instances of DelayedEnumeratorT.
If DelayedEnumerator were public, you could
Thanks
I have never tried to use the MultiCriteria API, but can I get the
same result from using that?
Another question - how much an overhead is to array? am I loosing
what I have gained from using FutureT.
On Jul 27, 12:33 am, Davy Brion ral...@davybrion.com wrote:
it's indeed not a lazy
I see NHibernate.Linq 1.0.0 GA src(http://sourceforge.net/projects/
nhibernate/files/) have Northwind.Entities using NHibernate Plugin for
Visual Studio 2005(http://sourceforge.net/projects/nhibernateaddin/),
The Tool Can't be used in VS2008,Has anyone update it? Have other
Tools?
Hi,
Call Session.Delete(object) never executes the DELETE SQL.
If I wrap it in a transaction - it does.
Additionally when I use Session.SaveOrUpdate(object) I don't need to wrap it
in transaction or Flush. It does execute the SQL.
Feels very inconsistent. Do I miss something?
I do not provide
So, when I use custom SQL and I join to an entity say Address... if no
Address is found NHibernate is going and making a second sql call for the
Address, and hence I'm ending up with an N+1 SELECT problem.
An example of this problem is here;
http://bit.ly/4boQqN
But I can summarize:
It
If you use MultiCriteria directly then you avoid the usage of
DelayedEnumerator, but you'll just get an untyped IList instance, where each
element within the IList instance is again another untyped IList instance.
You definitely won't notice a performance penalty from using ToArray or a
ToList or
17 matches
Mail list logo
