public inbox for [email protected]  

help / color / mirror / Atom feed
From: M Sarwar <[email protected]>
To: Paul Smith* <[email protected]>
To: [email protected] <[email protected]>
Subject: Re: The same result for with SPACE and without SPACE
Date: Thu, 15 Jun 2023 17:26:28 +0000
Message-ID: <DM4PR19MB597818A20E53C97BDB03AE8BD35BA@DM4PR19MB5978.namprd19.prod.outlook.com> (raw)
In-Reply-To: <[email protected]>
References: <DM4PR19MB5978EB964FA1C7B55FFCB02DD35AA@DM4PR19MB5978.namprd19.prod.outlook.com>
	<DM4PR19MB59782360E0C452810D70CBE8D35AA@DM4PR19MB5978.namprd19.prod.outlook.com>
	<[email protected]>
	<DM4PR19MB59784B518F25D2C2292CA3FBD35AA@DM4PR19MB5978.namprd19.prod.outlook.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<CAJXhg9ByRV9QPVcW5MPi2c20g948Oxt8qU1DrcVb51fFgTEj2A@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>

I guess behaviour is the same in Oracle as well.
Thanks,
Sarwar

________________________________
From: Paul Smith* <[email protected]>
Sent: Thursday, June 15, 2023 11:48 AM
To: [email protected] <[email protected]>
Subject: Re: The same result for with SPACE and without SPACE

On 15/06/2023 16:21, Wetmore, Matthew (CTR) wrote:

Before you kick me out of the group, can you please explain.



I thought the orig issue was that purposefully spaces/whitespace are being ignored (or not ignored.) in the select.  Maybe there was an email in the middle that I missed



create table matt_test (c1 int)



insert into matt_test  values ('123')



insert into matt_test  values (' 123')



insert into matt_test values ('123 ')



select c1 from matt_test where c1 = '123'

-- all 3 rows returned.



Is it expected behavior that all 3 rows would be returned (because the space isn’t an INT?)



Yes, that's totally expected behaviour. The "problem" is that it's pretty much obvious behaviour as well.

Your table is defined to store numbers not text.

So, when you do

     insert into matt_test  values ('123'); -- with any combination of leading/trailing spaces

Postgresql converts it to

    insert into matt_test values(123)

So, all three inserts you did are actually the same, and all store the *NUMBER* 123 in the table. Spaces are not part of the number, so are not stored

When you make the table store 'TEXT' or VARCHAR fields, then spaces ARE relevant for that type, so the data stored is different. For CHAR fields, they are space-padded or truncated as necessary to be the defined field size.

This is all pretty much basic SQL behaviour. Any correctly implemented SQL database server will behave exactly the same.


Paul


view thread (22+ messages)  latest in thread

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: The same result for with SPACE and without SPACE
  In-Reply-To: <DM4PR19MB597818A20E53C97BDB03AE8BD35BA@DM4PR19MB5978.namprd19.prod.outlook.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox