Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uWyQK-0045vE-Ot for pgsql-general@arkaria.postgresql.org; Wed, 02 Jul 2025 14:26:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uWyQH-001zQP-Bk for pgsql-general@arkaria.postgresql.org; Wed, 02 Jul 2025 14:26:53 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uWyQH-001zQE-0j for pgsql-general@lists.postgresql.org; Wed, 02 Jul 2025 14:26:53 +0000 Received: from mail-lj1-x236.google.com ([2a00:1450:4864:20::236]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uWyQF-005AV7-31 for pgsql-general@postgresql.org; Wed, 02 Jul 2025 14:26:52 +0000 Received: by mail-lj1-x236.google.com with SMTP id 38308e7fff4ca-32b3c292bb4so62483481fa.1 for ; Wed, 02 Jul 2025 07:26:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1751466410; x=1752071210; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=tgqBBqaT9gW1jjhJDvJEh0UjdE5Uj3NafDBdcp3OneA=; b=h6Zf4vxhe02vmfJjrHHoVhOlyLoE35ujXpbe0fBEyNZmObLSx62keWtzvaqOut8rH0 YtmNZ85T911E+hPH2EhjsfIsIcYmyShIsIAk+JvkapY+VMGhtkbb37ILFR3YNofU2FHA eXwBjI6K/4S1Eu8F7yWEDPN6PoxE61mjhxhr8KQR8XAq3HQlf7bI5iBjz9jUoeXmtFDC Zig+4ngschq/0PB9/BHNHNkWdoFz9lYPpyUdEgzYNaAZdd/Z3ldICBrQRB6RqP2fIeCw Z9sNp9PeOgBMLsZ84qWegO4etDCHjmZkoqK6IbgWG6jhrtU7DkjrFKcNseHbqhaLx85O h4qg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1751466410; x=1752071210; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=tgqBBqaT9gW1jjhJDvJEh0UjdE5Uj3NafDBdcp3OneA=; b=f348EjOaoBT7VI8dW1553tVrzH+yJYBBo104wvSYvLCbA1mgYMjmzE8dB9cjsIegmF +iYzOTa6qoqdLIsg8KRyGdv8TLL6GvfVuXKHwIn93eR4bJZAp/UoXa5wQSDmzgadRm79 q1a/UEJROfTaWGTZCwydppKUJ3MuulqL7v/tzX+4B1AtI+3XmV4dfeN6DdgwsuhTfBRS 2f3hJROcKgid0mBBJ8IkOSKZgU/C3nkQQEA/vWe0guVA6YpqnpbkVVTsNttGNy8e8mBl 9EN6Gn3eoFrcfUknFZDp0e6OJLvQWI22ZiBPFpnGDKm06D3pPWNiswhgbLsUbhCkDRQE BLCg== X-Gm-Message-State: AOJu0YxvZddr/0KNjWyKKQZdaUwe5iSU9wICI4YUcnn8BLZfmnA5UYLl pG14swwXzrLvqTmfOuxzgNH1iL+5dU+O2GyVYTj2y80V0iqvc1bSbH1sh8dUIicgaiTWebSVt3u ezUsUCZ55HFPBdj7WxVurnwagEl4w7P1YDw== X-Gm-Gg: ASbGncu0fPlzVwZZ4j0uNsU+UMhT1RDsPPaEkOmyo9XXb1Yt1wFMRleOhv1pgJbhjUJ P0aS8GovFPHokZket+VbstMcxP1pYR59IrLl5BebQTRaVJXPxpY1AxjC5QgmMflR4+UWC1Hf75F dohT8wRZUO3cJWNVO5IcbvjE+Looqqqe756aC4XD90W99RgGI54dUr4hF0/c3Nb0MweCuHWonqM g== X-Google-Smtp-Source: AGHT+IGDI6yQzjG7MgCcHjPzdGPYui00doJiSod7Td0RqwjUeaQUiXTv1BI84Dh4onhmvgOrKotuTaTlvA+AyYfQsnk= X-Received: by 2002:a2e:87d3:0:b0:32d:fd60:c82d with SMTP id 38308e7fff4ca-32e0006ab5amr9154341fa.24.1751466409689; Wed, 02 Jul 2025 07:26:49 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Durumdara Date: Wed, 2 Jul 2025 16:26:39 +0200 X-Gm-Features: Ac12FXw21yDp-j5bCDmA9iW173molv8hVjTJFjfCkaR-20-AYu3iJhV5nslCkv0 Message-ID: Subject: Re: PLPGSQL - store fetched records in array of record To: Ron Johnson Cc: pgsql-general Content-Type: multipart/alternative; boundary="0000000000002f8aa30638f30da7" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002f8aa30638f30da7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sorry. I forgot to mention that I have two arrays (records). One for the modifiable elements, and one for the checkable elements. If there is a conflict between the actual mod. item and one of the checkable items, the checkable item will move to the end of the modification list. And the actual mod. item starting time could be changed in this process. First I imagined a temporary table, but I felt this has too much overhead against an "in memory" array. UPDATE, INSERT, DELETE and reopen after each modification. Ron Johnson ezt =C3=ADrta (id=C5=91pont: 2025. j= =C3=BAl. 2., Sze, 15:29): > On Wed, Jul 2, 2025 at 8:21=E2=80=AFAM Durumdara wr= ote: > >> Hello! >> >> I have to store some fetched records into two lists (arrays) to work wit= h >> them. >> > > There's almost certainly a way to do what you need done without using > arrays. Might require a bit of rethinking, though. > > -- > Death to , and butter sauce. > Don't boil me, I'm still alive. > lobster! > --0000000000002f8aa30638f30da7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Sorry.=C2=A0
I forgot to mention that I have two array= s (records).

One for the modifiable elements, and one fo= r the checkable elements.

If there is a conflict= =C2=A0between the actual mod. item and one of the checkable items, the chec= kable item will move=C2=A0to the end of the modification list.
An= d the actual mod. item starting time could be changed in=C2=A0this process.=

First I imagined a temporary table, but I felt th= is has too much overhead against an "in memory" array.
UPDATE,= INSERT, DELETE and reopen after each modification.


Ron Johnson <ronljohnsonjr@gmail.com> ezt =C3=ADrta (id=C5=91pont: 2025.= j=C3=BAl. 2., Sze, 15:29):
On Wed, Jul 2, 2025 at 8:21= =E2=80=AFAM Durumdara <durumdara@gmail.com> wrote:
=
Hello!
I have to store some fetched records into=C2=A0two lists (arrays) to = work with them.

There's almos= t certainly a way to do what you=C2=A0need done without using arrays.=C2=A0= Might require a bit of rethinking, though.
=C2=A0
--
Death to <Redacted>, and butter sa= uce.
Don't boil me, I'm still alive.
<Redacted&= gt; lobster!
--0000000000002f8aa30638f30da7--