Search Postgresql Archives

Re: database design with temporary tables

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 29/08/2021 17:53, Adrian Klaver wrote:
On 8/29/21 9:38 AM, ourdiaspora wrote:

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Sunday, August 29th, 2021 at 5:30 PM, Adrian Klaver <adrian.klaver@xxxxxxxxxxx> wrote:

On 8/29/21 9:24 AM, Adrian Klaver wrote:


Whoops, unfinished thought. What I was going to ask is:

The above is not clear to me. Are you asking about the Postgres

documentation?


Yes, wanted to know relevant parts because often the first problem is to know which part of the (extensive) documentation to read...


From what I see it is basic operations; CREATE TABLE, SELECT, INSERT, UPDATE and COPY.

As I said in my previous post create a fairly detailed design flow first and from that you will see what operations you need to do and what part of the docs you need to look at.

+100 to this. Also, it's not clear from your description what is happening where - how much functionality is in the database, and how much at the web server. Are your users connecting directly to the database server? - or do they connect only to the web server, which then uses its own account on the database server? Get this clear in your own head and much of the rest will follow.

Ray.



--
Raymond O'Donnell // Galway // Ireland
ray@xxxxxxxxxxxx





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux