Re: Function PostgreSQL 9.2

From: "Mike Sofen" <msofen(at)runbox(dot)com>
To: "'Postgres General'" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Function PostgreSQL 9.2
Date: 2016-04-20 02:50:27
Message-ID: 01eb01d19aaf$66488cc0$32d9a640$@runbox.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

This is such a poorly designed, hacked together “thing” – it isn’t a database, it’s someone’s idea of how to store data when they don’t know how to store data, like they moved it from Access or Excel.

Just start over and design a proper relational schema with best practices and you’ll save, oh, perhaps 10 years of wasted effort and 12 million emails. This is as close to bandaids on bandaids on steroids that it comes. Really – rethink your solution model.

Mike

From: drum(dot)lucas(at)gmail(dot)com <mailto:drum(dot)lucas(at)gmail(dot)com> Sent: Tuesday, April 19, 2016 7:40 PM
Just forgot to say:

Does increment_client_code relate to users or some other table, say clients?

nope.. there is no link between them

If the users.code is empty/null, then the trigger has to get the last number from client_code_increment and put on the users.code column

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Albe Laurenz 2016-04-20 07:28:30 Re: Enhancement Request
Previous Message drum.lucas@gmail.com 2016-04-20 02:40:24 Re: Function PostgreSQL 9.2