**
FROM "order_bt" o
LEFT JOIN acc_ready( 'Invoice', app_period(), o ) acc_i ON acc_i.ready
LEFT JOIN acc_ready( 'Usage', app_period(), o ) acc_u ON acc_u.ready
What you can say about this proposition?
--
Best regards,
Eugen Konkov
uma ) filter (where nrow = 1) over (partition by agreement_id)
from intermediate
Wednesday, April 22, 2020, 10:05:19 AM, you wrote:
> Hello Andreas,
> Tuesday, April 21, 2020, 6:17:00 PM, you wrote:
>> On 4/21/20 5:06 PM, Eugen Konkov wrote:
>>> Hi. I read the thread.
esc nulls last,? detail_amount desc,? service_type nulls last,?
detail_id?)?) "me"" with ParamValues: 1='2020-08-01', 2='2', 3='2', 4=undef,
5='2', 6='3493', 7='10', 8='2', 9='2'] at
/home/kes/work/projects/tucha/monkeyman/lib/MaitreD/Controller/Cart.pm line 828
--
Best
3='2', 4=undef, 5='2',
6='3493', 7='10', 8='2', 9='2'] at
/home/kes/work/projects/tucha/monkeyman/lib/MaitreD/Controller/Cart.pm line 828
--
Best regards,
Eugen Konkov
f here also will be reported error value.
It will shed more light on what is comming wrong
Also would be useful if PG point at query where this bad value was calculated
or occur.
It this possible?
Thank you.
--
Best regards,
Eugen Konkov
ot understand those things =(
Thank you.
--
Best regards,
Eugen Konkov
the column be named?
Suppose it should be named 'as x'
> I think we'd be trying to manage a set of corner cases, and all because
> someone didn't want to put "as foo" in their query. And if we generate a
> column name in some cases and not in others there will be complaints of
> inconsistency.
> cheers
> andrew
> --
> Andrew Dunstan
> EDB: https://www.enterprisedb.com
--
Best regards,
Eugen Konkov
020, 9:17:28 PM, you wrote:
On Wed, Nov 11, 2020 at 12:12 PM Eugen Konkov <kes-...@yandex.ru> wrote:
> So I feature request to allow zero size step for cases when start point is equest to finish
> What do you think?
hm probably with step 0 we always should gene
Hello Bruce,
Wednesday, November 11, 2020, 5:56:08 PM, you wrote:
> On Mon, Nov 2, 2020 at 05:05:29PM +0200, Eugen Konkov wrote:
>> Hello Pgsql-hackers,
>>
>> When selecting data from json column it named as '?column?'
>> tucha=# select info->>'suma', docn fro
, despite on finish value.
Because with step 0 we always stay at current position, so there is
always should be just one value.
--
Best regards,
Eugen Konkov
ish
What do you think?
--
Best regards,
Eugen Konkov
1302
(5 rows)
Would it be useful this auto assigned name for column from json?
--
Best regards,
Eugen Konkov
Hello Andreas,
Tuesday, April 21, 2020, 6:17:00 PM, you wrote:
> On 4/21/20 5:06 PM, Eugen Konkov wrote:
>> Hi. I read the thread.
>>
>> Probably this fiddle will be helpful for testing:
>>
>> https://dbfiddle.uk/?rdbms=postgres_12=abe845142a5099d921d3729043fb8
may
be applied to window functions (did not check this for other functions thought)
--
Best regards,
Eugen Konkov
=97c05203af4c927ff9f206e164752767
Why Window-specific functions do not allow DISTINCT to be used within the
function argument list.?
Which problems are exists?
--
Best regards,
Eugen Konkov
mpress and actually store Zx5 into field
-- Delete this insert row
-- So user should get back that the value Z was deleted and not Zx5.
Correct?
but currently user will see Zx5, because next code:
OLD.value = uncompress( OLD.value );
does not effect RETURNING =(
--
Best regards,
Eugen Konkov
Hello Eugen,
> https://dbfiddle.uk/?rdbms=postgres_12=95ed9fab6870d7c4b6266ea4d93def13
sorry, forget to update link to the latest example:
https://dbfiddle.uk/?rdbms=postgres_12=8e114ccc9f15a30ca3115cdc6c70d247
--
Best regards,
Eugen Konkov
FAIL (behavior is not
expected)
This is inconsistent to allow modify output data for UPDATE and
restrict to do this for DELETE
Thank you
--
Best regards,
Eugen Konkov
Hello Eugen,
Saturday, November 9, 2019, 2:05:02 PM, you wrote:
> Hello Bruce,
> Friday, November 8, 2019, 12:28:18 AM, you wrote:
>> On Thu, Nov 7, 2019 at 04:26:55PM -0500, Bruce Momjian wrote:
>>> On Thu, Nov 7, 2019 at 11:24:29AM +0200, Eugen Konkov wrote:
>&g
Hello Bruce,
Friday, November 8, 2019, 12:28:18 AM, you wrote:
> On Thu, Nov 7, 2019 at 04:26:55PM -0500, Bruce Momjian wrote:
>> On Thu, Nov 7, 2019 at 11:24:29AM +0200, Eugen Konkov wrote:
>> > >> As far as allowing DELETE to modify the trigger row for RETURNING, I
d at first letter, without
> this the RETURNING rows **does not correspond actually deleted data**
> Thank you.
--
Best regards,
Eugen Konkov
NING". Becuase, as I have described at first letter, without
this the RETURNING rows **does not correspond actually deleted data**
Thank you.
--
Best regards,
Eugen Konkov
on of row?
--
Best regards,
Eugen Konkov
converted( I suppose ) to OPERATOR(
someplace.=, x, y, magic )
--
Best regards,
Eugen Konkov
Hi.
I have noticed that it would be cool to use '==' in place of 'IS NOT
DISTICT FROM'
What do you think about this crazy idea?
--
Best regards,
Eugen Konkov
;< this takes 11500ms
-- AND next_ots.consumed_period @> (ots.o).billed_to
WHERE ots.order_id IN ( 6154, 10805 )
id is not pushed for LEFT JOIN
I have attached plans:
--
Best regards,
Eugen Konkov
plans
Description: Binary data
(t.o).id = 6154 AND t.consumed_period @>
> '2019-04-01'::timestamptz -- This takes 2700ms
> More info is here: https://stackoverflow.com/q/57003113/4632019
--
Best regards,
Eugen Konkov
-01'::timestamptz
-- This takes 2ms
-- WHERE (t.o).id = 6154 AND t.consumed_period @>
'2019-04-01'::timestamptz -- This takes 2700ms
More info is here: https://stackoverflow.com/q/57003113/4632019
--
Best regards,
Eugen Konkov
---
[-infinity,infinity)
(1 row)
--
Best regards,
Eugen Konkov
that this function has no effect because
there is no transaction in progress
--
Best regards,
Eugen Konkov
30 matches
Mail list logo