| From: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
|---|---|
| To: | Steven Brown <swbrown(at)ucsd(dot)edu> |
| Cc: | Alban Hertroys <alban(at)magproductions(dot)nl>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Enforcing serial uniqueness? |
| Date: | 2006-03-22 13:48:03 |
| Message-ID: | 1143035283.23597.37.camel@coppola.muc.ecircle.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> Gaps are fine. All I want is safe uniqueness. What is an issue for me
> is a user having INSERT permission being able to shut down all INSERTs
> from everyone else until someone manually figures out what happened and
> fixes it, ditto for UPDATE permission on a sequence (which they need in
> order to use nextval so they know what id the row they inserted will
> have, right?), which seems extremely dangerous to me.
No doubt that you will be able to solve your problem by the permission
system somehow, but I wonder how stable a system can be if you allow
users to insert directly to the data base ?
If you would have a set of fixed/approved SQLs which are controlled by
an application (and the application in turn controlled by responsible
developers you trust), and users can only access data through that
application, these kind of problems won't occur at all...
Cheers,
Csaba.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Buttafuoco | 2006-03-22 13:49:48 | Re: Enforcing serial uniqueness? |
| Previous Message | Steven Brown | 2006-03-22 13:44:06 | Re: Enforcing serial uniqueness? |