Re: AW: AW: Cast INTEGER to BIT confusion

On Thu, 17 Aug 2023 at 19:09, GF wrote: > > Erik, > The could be a possible solution, if you could play with search_path... > > (sorry, Erik, obviously my message was intended to Markus)

Re: AW: AW: Cast INTEGER to BIT confusion

Erik, The could be a possible solution, if you could play with search_path... You could mirror all the original schema onto another one with views that have the original table names. For all tables that need some special treatment you can then write instead-of triggers, while all other views are up

Re: AW: AW: Cast INTEGER to BIT confusion

> On 17/08/2023 15:18 CEST Tom Lane wrote: > > That's probably because the grammar uses SystemTypeName (effectively > prepending "pg_catalog.") for any type that has special syntax called > out in the SQL standard. You could get around that in various ways, > but they all involve changing the way

Re: AW: AW: Cast INTEGER to BIT confusion

Dienstag, 15. August 2023 16:28 > An: [Quipsy] Markus Karg ; pgsql-general@lists.postgresql.org > Betreff: Re: AW: Cast INTEGER to BIT confusion > > > On 15/08/2023 14:02 CEST [Quipsy] Markus Karg wrote: > > > > I just tried out your proposal on PostgreSQL 15.3 and th

Re: Cast INTEGER to BIT confusion

On Tuesday, August 15, 2023, Erik Wienhold wrote: > > On 15/08/2023 10:49 CEST [Quipsy] Markus Karg wrote: > > > > Hello PostgreSQL Community, > > > > I like to store just a single bit but that can be either 1 or 0, so I > tried > > You could create a custom domain if you're only interested in v

Re: AW: AW: Cast INTEGER to BIT confusion

"[Quipsy] Markus Karg" writes: > I am giving up. While even `SELECT current_schemas(true)` correctly prints > `xxx, pg_catalog` it still uses the original bit type. This is completely NOT > as described in the documentation, where it is clearly told that pg_catalog > only is searched immediatel

Re: Cast INTEGER to BIT confusion

> On 17/08/2023 14:57 CEST rob stone wrote: > > It works thus:- > > postgres 15.4 =# CREATE TABLE T (c BIT); > CREATE TABLE > postgres 15.4 =# insert into T values (B'1'); > INSERT 0 1 > postgres 15.4 =# select * from t; > c > --- > 1 > (1 row) > > See section 9.6 in the doco. But Markus wrote

Re: Cast INTEGER to BIT confusion

Hello, On Tue, 2023-08-15 at 08:49 +, [Quipsy] Markus Karg wrote: > > > > Hello PostgreSQL Community, >   > I have 25+ years of experience with some other RDBMS, but I am a > PostgreSQL starter, so I assume the following is rather a simple > beginner’s question…: >   > I like to store jus

AW: AW: Cast INTEGER to BIT confusion

Betreff: Re: AW: Cast INTEGER to BIT confusion > On 15/08/2023 14:02 CEST [Quipsy] Markus Karg wrote: > > I just tried out your proposal on PostgreSQL 15.3 and this is the result: > > ERROR: column "c" is of type bit but expression is of type integer > LINE

Re: Cast INTEGER to BIT confusion

On Tue, Aug 15, 2023 at 4:49 AM [Quipsy] Markus Karg wrote: > > CREATE TABLE T (c BIT); > > INSERT INTO T VALUES (1); > > -- I MUST NOT change both lines in any way as these are part of a > third-party application! > That is quite the requirement! I hope that the rest of the application is more

Re: AW: Cast INTEGER to BIT confusion

^ > HINT: You will need to rewrite or cast the expression. > > Apparently the search path is ignored?! > > -Ursprüngliche Nachricht- > Von: Erik Wienhold > Gesendet: Dienstag, 15. August 2023 13:48 > An: [Quipsy] Markus Karg ; pgsql-general@lists.post

Re: AW: Cast INTEGER to BIT confusion

> On 15/08/2023 13:59 CEST [Quipsy] Markus Karg wrote: > > Is setting the search path something that has to be done for each new > connection / each user, or is this something static and global for the > database? The search path is set per connection and the initial search path can be configured

AW: Cast INTEGER to BIT confusion

the search path is ignored?! -Markus -Ursprüngliche Nachricht- Von: Erik Wienhold Gesendet: Dienstag, 15. August 2023 13:48 An: [Quipsy] Markus Karg ; pgsql-general@lists.postgresql.org Betreff: Re: Cast INTEGER to BIT confusion > On 15/08/2023 10:49 CEST [Quipsy] Markus Karg wro

AW: Cast INTEGER to BIT confusion

the database? Thanks a lot! -Markus -Ursprüngliche Nachricht- Von: Erik Wienhold Gesendet: Dienstag, 15. August 2023 13:48 An: [Quipsy] Markus Karg ; pgsql-general@lists.postgresql.org Betreff: Re: Cast INTEGER to BIT confusion > On 15/08/2023 10:49 CEST [Quipsy] Markus Karg wr

Re: Cast INTEGER to BIT confusion

> On 15/08/2023 10:49 CEST [Quipsy] Markus Karg wrote: > > Hello PostgreSQL Community, > > I like to store just a single bit but that can be either 1 or 0, so I tried > to do this: > > CREATE TABLE T (c BIT); > INSERT INTO T VALUES (1); > -- I MUST NOT change both lines in any way as these are par

Cast INTEGER to BIT confusion

Hello PostgreSQL Community, I have 25+ years of experience with some other RDBMS, but I am a PostgreSQL starter, so I assume the following is rather a simple beginner's question...: I like to store just a single bit but that can be either 1 or 0, so I tried to do this: CREATE TABLE T (c BIT);