Weird, but apparently not a bug. From
https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-SYNTAX-CONSTANTS
> Two string constants that are only separated by whitespace with at
> least one newline are concatenated and effectively treated as if the
> string had been written as one co
On Mon, 17 Feb 2020 16:49:27 +0100
Matthias Apitz wrote:
> I spend today some hours to nail down and insert problem into our
> database with DBI like:
>
>my $rc = $my_dbh->do($my_sqlstatement);
>
> which returns 1 in $rc (which the following flow in our script took
> as an error).
The DBI d
On Thu, 2 Jul 2020 11:03:37 -0400
stan wrote:
> my $sth = $dbh->prepare($stmt);
> my $rv = $sth->execute() or die $DBI::errstr;
that ``or die`` means: if the result of the ``execute`` is false
(which only happens on error), throw an exception (which, as you
noticed, terminates the process unless
If you can use bash, or set up some redirections from whatever you're
using to execute ``psql``, you can do::
$ psql somedb --set num=42 <<<'select :num'
Timing is on.
Expanded display is used automatically.
Line style is unicode.
Border style is 2.
┌──┐
│ ?column? │
├─
On 2022-12-10 Eagna wrote:
> This should be very (very) easy - I don't know what I'm missing -
> I've done quite complex regular expressions before and I don't know
> what I'm doing wrong. Brain burping this morning!
You're missing that:
* `regexp_replace` doesn't work like that, at all
* your l
On 2022-12-10 Eagna wrote:
> If you have any ideas how it could be done indirectly/different
> strategy - I'm all ears.
You haven't explained what you're trying to accomplish.
--
Dakkar -
GPG public key fingerprint = A071 E618 DD2C 5901 9574
On 2022-12-10 "Peter J. Holzer" wrote:
> > * your logic only works by accident for some languages (try to
> > upcase a `ß` or a `ı`)
>
> This is also true of upper() and lower() and SQL does provide those.
Well…
> select upper('ı');
┌───┐
│ upper │
├───┤
│ I │
└───┘
(1 row)
>
On 2022-12-10 Eagna wrote:
> Hi again, and thanks for sticking with this.
> > You haven't explained what you're trying to accomplish.
>
> Ok.
>
> CREATE TABLE test(x TEXT);
>
> INSERT INTO test VALUES ('abc');
>
> SELECT REGEXP_REPLACE(x, '', '', 'g')
> FROM test;
>
> Expected result: AB
On 2022-12-10 "Peter J. Holzer" wrote:
> So, what's the point you are trying to make?
I suspect I mis-understood a thing you wrote… ignore me.
> > Of course all of this is dependent of locale, too.
> Right. But why would that be different for regexp_replace than for
> upper/lower?
I was tryin
Some experimentation:
> \pset null '((null))'
> select jsonb_set('{"foo":1}'::jsonb,'{bar}','null'::jsonb,true);
┌─┐
│jsonb_set│
├─┤
│ {"bar": null, "foo": 1} │
└─┘
> select jsonb_set('{"foo":1}'::jsonb,'{ba
Aha! I had mis-understood how "strict"-ness works.
Thank you David for the explanation!
Thomas: the two main pieces are these:
> SQL null and json null are represented differently
As far as SQL is concerned, `'null'::jsonb` is a valid (non-`NULL`)
value. The SQL part of Postgres doesn't "look i
On 2023-07-12 Johnathan Tiamoh wrote:
> I wish to find out if there is a way to reset all users in Postgresql
> password to the same password at once.
I guess you could update the `pg_catalog.pg_authid` table, see
https://www.postgresql.org/docs/15/catalog-pg-authid.html
--
Dakkar -
On 2021-04-02 Joao Miguel Ferreira
wrote:
> Is it possible, in PL/pgSQL, to pass an argument to a function which
> is actually a "query skeleton" that the method will "fill in the
> blanks" and execute it or return it to the caller after ?
you probably want to use the ``EXECUTE`` command:
https:/
On 17 May 2021 13:27:40 -
haman...@t-online.de wrote:
> in unicode letter ä exists in two versions - linux and windows use a
> composite whereas macos prefers the decomposed form. Is there any way
> to make a semi-exact match that accepts both variants?
You should probably normalise the string
On 17 May 2021 13:27:40 -
haman...@t-online.de wrote:
> in unicode letter ä exists in two versions - linux and windows use a
> composite whereas macos prefers the decomposed form. Is there any
> way to make a semi-exact match that accepts both variants?
Actually, re-reading your request, you w
On Mon, 17 May 2021 15:45:00 +0200
Matthias Apitz wrote:
> There is only *one* codepoint for the German letter a Umlaut:
> LATIN SMALL LETTER A WITH DIAERESI U+00E4
True. On the other hand, the sequence:
* U+0061 LATIN SMALL LETTER A
* U+0308 COMBINING DIAERESIS
will render exactly the same gly
I realise this may not be applicable to the original problem, but
non-deterministic collations seems to offer a solution::
dakkar@[local] dakkar=> create collation "en-US-ins-icu" (
provider=icu,
locale='en-US-u-ks-level2',
deterministic=false
);
dakkar@[l
On 2024-10-21 Anatolii Smolianinov wrote:
> date(1) does not set timezone dir: but it uses TZ, and, in man, it
> refers to tzselect:
> > use tzselect to find TZ"
That's an imperative "use", not an indicative. In other words: the
user, to find an appropriate value for `TZ`, should run the command
On Mon, 18 Nov 2024 15:37:57 +0100
Moreno Andreo wrote:
> If a column appears in the WHERE clause (and so it should be placed
> in index), in case it is "processed" in a function (see below), is it
> possible to insert this function to further narrow down things?
You probably want to look at
ht
Hello all!
I have a primary+replica PostgreSQL that I think work fine.
I created the replica's data directory using::
pg_basebackup -D $datadir -h $primary_host -U $replicauser \
--write-recovery-conf \
--create-slot --slot=$slotname
after creating the u
20 matches
Mail list logo
