I did not question the difference between bitwise and logical Boolean
operators in programming languages.
I just wanted to spot that there is no equivalent in SQL of the well-
defined short-circuit operators in C# where you can e.g. first check
if a value is not null and then evaluate some propert
Default vs 2010 web application did not create namespace for any of the
classes, I created manually and worked like a charm. Thanks Michele saved me
alot of time.
On 5 Ara 2011, at 16:02, Michele Lepri wrote:
> My 2 cents: do you have any classes defined in an empty namespace?
>
>
> Il 05/12
I've got a queer bug that I can't find any info on.
Just to be clear, this is NOT a derived class proxy question (at
least, I don't believe it is).
I have two unrelated classes "Certification" and "DuesCategory". Both
inherit from other abstract classes but they are independent of each
other. The
Well, I think David has summarized it all.
> ...
> But as I wrote: *an SQL AND or OR operator is no AndElse or OrElse
> operator because the order of evaluation is not determined by the
> operator but by the execution engine. *And I don't know if the engine
> really guarantees the execution of
Try
mapper.AddMappings(typeof().Assembly.Get
Types());
Rippo
From: nhusers@googlegroups.com [mailto:nhusers@googlegroups.com] On Behalf
Of Mert Ece
Sent: 05 December 2011 13:34
To: nhusers@googlegroups.com
Subject: [nhusers] Asp.NET mapping by code error
Hi,
I am trying to wri
My 2 cents: do you have any classes defined in an empty namespace?
Il 05/12/2011 14:34, Mert Ece ha scritto:
> Hi,
>
> I am trying to write a web application in ASP.NET using 3.2 mapping by
> code. I copied the same mappings and classes from my working winforms
> application but got the error be
Hi,
I am trying to write a web application in ASP.NET using 3.2 mapping by code.
I copied the same mappings and classes from my working winforms application
but got the error below in mapping stage. Is there any specific
configuration or something I have to do in web application in order
nhiber
Hi
NHibernate now supports JPA (called NPersistence or NPA for the .NET
platform) including JPA annotations.
It is the best way to specify relations and have your code portable
for other vendors as well.
check it out:
www.npersistence.com
--
You received this message because you are subscribed to
Hi
I had a similiar problem. I'm using NH 3.2 and indeed it returns 0
rows.
before
=
var lista = session.QueryOver
.Take(PageSize)
.Skip(page * PageSize)
.List();
NO RESULTS0 RECORDS
I looked at the NHprof profiler and analyzed the select statement that
was made to oracle...
and I solv
On 05.12.2011 11:51, CSharper wrote:
Yes, but they are meant for integral data types where they actually
make a difference. The documentation link you have in there says it
works with two bits in 2008 R2 also but I tried with 2008 and it did
not work with bits there.
But as I wrote: an SQL AND or
Yes, but they are meant for integral data types where they actually
make a difference. The documentation link you have in there says it
works with two bits in 2008 R2 also but I tried with 2008 and it did
not work with bits there.
But as I wrote: an SQL AND or OR operator is no AndElse or OrElse
op
2011/12/5 Oskar Berggren :
> 2011/12/4 sdhjl2000 :
>> it works well in 3.1 version which take's param should be the pageize
>> of the container,but after i upgrade the dll,take's param need to the
>> end index of current page otherwise it return zero record, any tips
>> or trick?
>>
>
>
> Sounds
2011/12/4 sdhjl2000 :
> it works well in 3.1 version which take's param should be the pageize
> of the container,but after i upgrade the dll,take's param need to the
> end index of current page otherwise it return zero record, any tips
> or trick?
>
Sounds like a bug. Could you provide a short
On Mon, Dec 5, 2011 at 3:44 PM, CSharper wrote:
> Maybe that's the way it's currently working with NHibernate but for
> Boolean operands, both operators should work in a query language
> targeting SQL in the background.
Doesn't SQL have both operators: logical (
http://msdn.microsoft.com/en-us/
@Max:
Maybe that's the way it's currently working with NHibernate but for
Boolean operands, both operators should work in a query language
targeting SQL in the background.
The operator behaviour of SQL is neither exactly like the short
circuit && (or ||) nor the bitwise Boolean & (or |) operators.
15 matches
Mail list logo
