Hi all
Someone earlier today pointed me in the direction of the following problem
with
LinqToSql<https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=363290&wa=wsignin1.0>.
In summary, if a string or decimal/numeric has varying lengths in the
queries, each different length is passed as a differently defined parameter.
Each of these variations results in a different item being compiled and
stored in the procedure cache.
Thus:
from f in foo where name == "asd"
from f in foo where name == "asdf"
and
from f in foo where value == 5.2
from f in foo where value == 5.26
from f in foo where value == 25.2
from f in foo where value == 25.26
all result in different items in the cache (in the string example because
the first one has @p0 NVARCHAR(3) and the second has @p0 NVARCHAR(4)).
I'm no expert in this, so forgive me if I've misrepresented this. The
examples are those given to me earlier.
I'm happy to investigate myself (so tell me to if I should), but does
NHibernate exhibit the same behaviour, or are the parameters scoped to the
column type?
While bloat is not ideal in any situation, if NHibernate does exhibit this,
is this a valid concern?
Look forward to your input (even if it is just to investigate myself :p).
--
Ben Hart
http://blog.benhartonline.com/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---
