Dave Coventry wrote:
> I have a database with all of the particulars of our students and I am
> adding a table that will contain all of the courses and the grades
> attained by the students.
>
> All this information is to be read by just about everybody, and the
> bulk of the data will be written
On Wed, Jun 18, 2008 at 1:11 PM, David <[EMAIL PROTECTED]> wrote:
> Hi Dave.
>
> Did you intentionally mail me off-list? On-list is generally better so
> other people can give suggestions.
No, sorry.
I've just joined the list and am a little unused to it's mechanics.
I appreciate that any solutio
Hi Dave.
Did you intentionally mail me off-list? On-list is generally better so
other people can give suggestions.
On Wed, Jun 18, 2008 at 12:04 PM, Dave Coventry <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 18, 2008 at 11:33 AM, David <[EMAIL PROTECTED]> wrote:
>> How about setting up separate datab
Dave Coventry wrote:
> Hi.
>
> I have a database with all of the particulars of our students and I am
> adding a table that will contain all of the courses and the grades
> attained by the students.
[snip]
> The marks (or grades) of the students are a different matter and we
> want to restrict c
On Wed, Jun 18, 2008 at 11:04 AM, Dave Coventry <[EMAIL PROTECTED]> wrote:
[...]
> The marks (or grades) of the students are a different matter and we
> want to restrict changes to this data to a very few people.
>
How about setting up separate database users/groups (aka roles in
newer postgresq
Hi.
I have a database with all of the particulars of our students and I am
adding a table that will contain all of the courses and the grades
attained by the students.
All this information is to be read by just about everybody, and the
bulk of the data will be written by several clerks, and, whil
