also save myself loading the dump from the sql-file. The more I
think about it, the more I love this idea.
Thanks a lot, Wolfgang
--
Wolfgang Rißler
mailto: wolfgang.riss...@freenet.de
mobil: +49 1520 9191759
- may the source be with you -
is SET standard_conforming_strings =
on;) as a pqxx-transaction...
--
Wolfgang Rißler
mailto: wolfgang.riss...@freenet.de
mobil: +49 1520 9191759
- may the source be with you -
Dominique Devienne:
I wish for DB-specific ROLEs BTW...
Same here. That would be so useful.
Hello community,
since we need a libpq for postgres v13 for a win32 project, and I did
not find a binary package, I tried to compile my own postgres v13 win32
with MSVisualStudio 2019.
This works so far, as described in the docs.
I also could add the most extensions in the config.pl (without
Am 01.05.2021 um 18:26 schrieb Adrian Klaver:
On 5/1/21 3:59 AM, Wolfgang Rißler wrote:
This is my problem, I completely dont know, how to start compiling my
own actual 32bit libpq on windows (and I would like to do it with VS
2019).
For libpqxx there have been some hints how to do so
Am 30.04.2021 um 16:16 schrieb Tom Lane:
=?UTF-8?Q?Wolfgang_Ri=c3=9fler?= writes:
The problem is, that our application (IDE MS-VisualStudio, C++) has to
be 32bit, because of some old 32bit-dll's, which we cant kick out at the
moment.
So I compiled a libpqxx with the last 32bit libpq (which is
Am 30.04.2021 um 13:41 schrieb Laurenz Albe:
> Please reply to the list> Sorry my mistake, I fixed this.
> On Fri, 2021-04-30 at 13:20 +0200, Wolfgang Rißler wrote:
>> Thanks for answering, but
>> I didn't ask for a PostgreSQL client. I asked for the c-language-lib
>>
Am 30.04.2021 um 13:00 schrieb Laurenz Albe:
On Fri, 2021-04-30 at 10:49 +0200, Wolfgang Rißler wrote:
we are (unfortunately) on windows with our DB and our application.
Now we want to switch to a new version of Postgres, because we want to
use logical replication (to replace our old Postgres
Hello community,
we are (unfortunately) on windows with our DB and our application.
Now we want to switch to a new version of Postgres, because we want to
use logical replication (to replace our old Postgres 8.3 with
slony-replication).
The problem is, that our application (IDE
e.
In my case I'm seeding a postgres docker container with settings and
data on first launch. The database name is passed to the container via
environment variable. But, I'm sure there are other use-cases where code
should be written once, but be executed in different databases.
Best,
Wolfgang
to anyone else?
Best,
Wolfgang
Tom Lane:
I think you're on fairly shaky ground here. Generally speaking, a CTE
will be executed/read only when the parent query needs the next row from
it. Your examples ensure that the CTE is read before the parent query's
results are computed; but in realistic usage you'd presumably be
to problems with privileges / permissions?
Any input/insight would be helpful.
Thanks
Wolfgang
[1]: https://postgrest.org
}
}
foreach d $GD(data) {
# the work
}
$$ language pltcl;
Does this make any difference - i.e. how often will parsing the data happen?
Best regards
Wolfgang Hamann
14 matches
Mail list logo