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

  • SEARCH
  • Home
  • 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 577061
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T14:06:47+00:00 2026-05-13T14:06:47+00:00

I am trying to determine that standard SQL behaviour for comparing a number to

  • 0

I am trying to determine that standard SQL behaviour for comparing a number to a character or string version of the same number. Does SELECT 1 = '1' (or the like) always return some sort of “truthy” value (true, 1, 't', etc.)? I have confirmed as much on PostgreSQL and MySQL, but I cannot find a resource for SQL as a whole.

Update: The purpose for the question is that I’m trying to figure out if using a number, without the quotes, will work when selecting/inserting/updating/etc. from a non-numeric field whose value is a number.

  • 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-13T14:06:47+00:00Added an answer on May 13, 2026 at 2:06 pm

    SELECT 1='1' gives TRUE since '1' is a correct constructor for INT in all implementation known to me.

    But SQL uses strict typing, see that:

    # SELECT 1=CAST('1' AS TEXT);
    ERROR:  operator does not exist: integer = text
    LINE 1: SELECT 1=CAST('1' AS TEXT);
                    ^
    HINT:  No operator matches the given name and argument type(s). You might need to add  explicit type casts.
    

    Regarding the standard (SQL 92, 99 & 2003) it seems to be wrong:

         <literal> ::=
                <signed numeric literal>
              | <general literal>
    
         <general literal> ::=
                <character string literal>
              | <national character string literal>
              | <bit string literal>
              | <hex string literal>
              | <datetime literal>
              | <interval literal>
    
         <signed numeric literal> ::=
              [ <sign> ] <unsigned numeric literal>
    
         <unsigned numeric literal> ::=
                <exact numeric literal>
              | <approximate numeric literal>
    
         <exact numeric literal> ::=
                <unsigned integer> [ <period> [ <unsigned integer> ] ]
              | <period> <unsigned integer>
    
         <unsigned integer> ::= <digit>...
    
         <character string literal> ::=
              [ <introducer><character set specification> ]
              <quote> [ <character representation>... ] <quote>
                [ { <separator>... <quote> [ <character representation>... ] <quote> }... ]
    

    because <quote> is only contained in <bit string literal>, <hex string literal>, … but not in numeric literals…

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

Sidebar

Related Questions

I'm trying to write a function that is able to determine whether a string
For a game I'm trying to determine the frequency that a certain # will
What I'm trying to achieve is to determine if the Postscript that I'm parsing
I am trying to store a large amount of boolean information that is determined
I'm trying to determine if there's a way in Visual Basic 2008 (Express edition
I am trying to determine the best time efficient algorithm to accomplish the task
I'm trying to determine, based on the result of this call, if it was
I'm trying to determine the best way to truncate or drop extra decimal places
I have been trying to determine a best case solution for registering a COM
I'm trying to determine if the user is using 24 hour or 12 hour

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.