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 938359
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 15, 20262026-05-15T21:37:52+00:00 2026-05-15T21:37:52+00:00

I have a legacy database with a field which contains some parentheses, like red(b).

  • 0

I have a legacy database with a field which contains some parentheses, like “red(b)”.

But if I try to query for that value, the parentheses come out encoded.

This query:

select * from table where field1 = "red(b)" 

Becomes this query:

select * from table where field1 = "red & #40; b & #41; " 

(I put a space between the & and # so it would show).

This return no rows.

Any ideas on how to handle this?

  • 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-15T21:37:53+00:00Added an answer on May 15, 2026 at 9:37 pm

    Hey Nick, thank for your help.

    As it turned out, the encoding took place between routing.php and my controller. So all I had to do was reverse it at the controller to eliminate the encoded parentheses. The query is working great now.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I currently have a database that gets updated from a legacy application. I'd like
We have some legacy code that needs to identify in the Page_Load which event
I have this legacy database for which I'm building a custom viewer using Linq
I have to connect to a legacy postgres database which has ENCODING = 'SQL_ASCII';
I have a name in a database, lets say its DFectuoso and some legacy
I am using NHibernate's SchemaExport to create my database schema. I have 1 legacy
I have a legacy C++ module that offers encryption/decryption using the openssl library (DES
I have a legacy VB6 application that was built using MSDE. As many client's
I have a legacy WinForms Mdi App in VB.Net 2.0 which I am adding
I have legacy asp.net 1.1 website. It has a very poor VB layered achitecture.

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.