Le 11 juin 2021 19:47:09 GMT+02:00, Nikolay Samokhvalov
a écrit :
>My thoughts:
>https://twitter.com/samokhvalov/status/1403408281389789189.
>Apologies for top-posting.
So now, we can have a thread split over two different places and tools...
Hello,
Is there a way to replace select * fileds in result ?
I have select qw.* from table but I want field for example mm to be
replaced with custom value like:
select qw.*, case whem length(qw.mm) > 0 THEN COALESCE(SUBSTRING(qw.mm,
1, 1), '') ELSE qw.mm END AS qw.mm
Is there some way to
On Saturday, June 12, 2021, Condor wrote:
>
> Hello,
>
> Is there a way to replace select * fileds in result ?
> I have select qw.* from table but I want field for example mm to be
> replaced with custom value like:
>
> select qw.*, case whem length(qw.mm) > 0 THEN COALESCE(SUBSTRING(qw.mm,
> 1,
On 12-06-2021 11:13, David G. Johnston wrote:
On Saturday, June 12, 2021, Condor wrote:
Hello,
Is there a way to replace select * fileds in result ?
I have select qw.* from table but I want field for example mm to be
replaced with custom value like:
select qw.*, case whem length(qw.mm) > 0
> On 12 Jun 2021, at 10:00, Condor wrote:
>
> select qw.*, case whem length(qw.mm) > 0 THEN COALESCE(SUBSTRING(qw.mm, 1,
> 1), '') ELSE qw.mm END AS qw.mm
A little off-topic, but isn’t that a roundabout way of writing just this?:
select qw.*, coalesce(substring(qw.mm, 1, 1), '') as
Hi Team,
I want to execute some queries on postgres and generate the reports
containing the resultset on client side for user in the most efficient way.
The data can be of 1 gb also.
Could you please help.
Thanks and regards,
Shubham
test=# create table t(id int, value text);
CREATE TABLE
test=# insert into t select x, x::text from generate_series(1, 1000) x;
INSERT 0 1000
test=# COPY (select * from t where id < 50 order by id desc) TO
'/tmp/report.csv' DELIMITER ',' CSV HEADER; copy out the results via
a view or sql d
correction,
i kind of recollected this as my own problem of a client wanting 100k rows
worth data downloadable.
we finally decided with csv dump and upload to object store, from where the
client would download the file.
all other options like web ui with pagination etc were resulting in memory
iss
On 2021-06-11 14:37:57 +0200, Marc Millas wrote:
> anyway, my original post was about the fact that we must create a PK based on
> some kind of work around the limited btree length behaviour thus creating an
> index that will never be of any use, just for technical reasons.
Actually, that index wi
