Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6583977
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 25, 20262026-05-25T16:28:47+00:00 2026-05-25T16:28:47+00:00

Whilst SQL Server is perfectly comfortable doing: where Id like ‘45%’ (id being an

  • 0

Whilst SQL Server is perfectly comfortable doing:

where Id like '45%'

(id being an int), NH will complain as it will still try to send the compare value into sql as a SqlParameter of type int when doing:

q.WhereRestrictionOn(cl => cl.CompanyId).IsLike(companyIdFilter)

So how to get round it with the new QueryOver API?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-25T16:28:48+00:00Added an answer on May 25, 2026 at 4:28 pm

    After some digging around and and trial and error, this does the trick:

    q.Where(Expression.Like(
       Projections.Cast(
         NHibernateUtil.String,
         Projections.Property<ChangeLog>(cl => cl.CompanyId)), 
       companyIdFilter.Value.ToString(),  
       MatchMode.Start
    ));
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Whilst working on a SQL Server 2008 database project in Visual Studio 2010 I
I've outgrown the Sql Server custom actions available in WiX, so I'm taking the
I'm currently developing a C# app with an SQL Server DB back-end. I'm approaching
I have got hold of a sql server 2008 developer edition and this is
I have following piece of sql, whilst it is functioning as expected, it is
Is it possible to reference a .NET Assembly from a SQL Server Stored procedure
We have a SQL 2005 database server which uses high safety (synchronous, no automatic
We have a .NET 2.0 winforms app that connects to a SQL Server 2005
It's a pretty standard setup, WinForms client > Self-serving Business/Data layer > SQL Server
Whilst on the surface this question looks like it should be on serverfault.com I

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.