Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] Array assignment behavior (was Re: Stored procedure array limits)

From: "John D(dot) Burger" <john(at)mitre(dot)org>
To: Postgres General <pgsql-general(at)postgresql(dot)org>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [GENERAL] Array assignment behavior (was Re: Stored procedure array limits)
Date: 2006-09-29 16:40:48
Message-ID: CA0C32E2-2371-4297-83AD-2ED9A14E0513@mitre.org (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-generalpgsql-hackers
>> As of 8.2 we could allow assignment to
>> arbitrary positions by filling the intermediate positions with nulls.
>> The code hasn't actually been changed to allow that, but it's  
>> something
>> we could consider doing now.
>
> At first blush, this strikes me as a bit too magical/implicit. Are  
> there other languages where sequences behave similarly?

 > perl -e '@A = (1, 2, 3); print "@A\n"; $A[10] = 10; print "@A\n";'
1 2 3
1 2 3        10

- John D. Burger
   MITRE


In response to

Responses

pgsql-hackers by date

Next:From: Andreas PflugDate: 2006-09-29 16:49:17
Subject: Re: Backup and restore through JDBC
Previous:From: Casey DuncanDate: 2006-09-29 16:35:25
Subject: Re: [GENERAL] Array assignment behavior (was Re: Stored procedure array limits)

pgsql-admin by date

Next:From: Paul B. AndersonDate: 2006-09-29 17:08:15
Subject: Re: Array assignment behavior (was Re: Stored procedure array
Previous:From: Casey DuncanDate: 2006-09-29 16:35:25
Subject: Re: [GENERAL] Array assignment behavior (was Re: Stored procedure array limits)

pgsql-general by date

Next:From: rloefgrenDate: 2006-09-29 16:51:09
Subject: alter integer field to serial integer primary key
Previous:From: John D. BurgerDate: 2006-09-29 16:37:58
Subject: Re: Expected accuracy of planner statistics

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group