On Wed, Mar 9, 2016 at 4:53 PM, Alexander Farber wrote:
> Hello Chris,
>
> On Wed, Mar 9, 2016 at 4:42 PM, Chris Travers
> wrote:
>
>>
>>
>> On Wed, Mar 9, 2016 at 1:10 PM, Alexander Farber <
>> alexander.far...@gmail.com> wrote:
>>
>>>
>>>
Hello Chris,
On Wed, Mar 9, 2016 at 4:42 PM, Chris Travers
wrote:
>
>
> On Wed, Mar 9, 2016 at 1:10 PM, Alexander Farber <
> alexander.far...@gmail.com> wrote:
>
>>
>> what is please the most efficient way to delete a slice from the start of
>> a longer array (after I
On Wed, Mar 9, 2016 at 1:10 PM, Alexander Farber wrote:
> Hello fellow PostgreSQL users,
>
> what is please the most efficient way to delete a slice from the start of
> a longer array (after I have copied it to another array)?
>
> Do I really have to copy a large
Hello Mike,
On Wed, Mar 9, 2016 at 2:42 PM, Mike Sofen wrote:
>
> Have you considered a normal (relational), non-array-based data model for
this app (2 or 3 tables in a 1:M/M:M) instead of the single table model
you’ve shown? That would then allow you to use normal sql
>>Alexander Farber wrote on Wednesday, March 09, 2016 4:11 AM
Hello fellow PostgreSQL users,
what is please the most efficient way to delete a slice from the start of a
longer array (after I have copied it to another array)?
Do I really have to copy a large slice of the array to itself,
Hello fellow PostgreSQL users,
what is please the most efficient way to delete a slice from the start of a
longer array (after I have copied it to another array)?
Do I really have to copy a large slice of the array to itself, like in the
last line here:
pile_array := pile_array ||