From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Using aclitem[] at application layer |
Date: | 2011-01-11 00:21:18 |
Message-ID: | 2920.1294705278@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"A.M." <agentm(at)themactionfaction(dot)com> writes:
> In an attempt to implement ACLs at the application layer (for resources stored outside of the database), I am evaluating using aclitem[] as a column type. All the functions I would need seem to be in place: aclcontains, aclexplode, aclinsert, aclitemeq, aclitemin, aclitemout, aclremove, but they are conspicuously missing from the documentation (http://www.mail-archive.com/pgsql-patches(at)postgresql(dot)org/msg03400.html) so I wonder if there are any caveats or hurdles which would make me consider writing my own type.
Other than the fact that we'd feel free to change the behavior of any or
all of that with no notice?
aclitem is an internal type. If you depend on its behavior, you'll have
only yourself to blame if your application fails in the future.
(I probably wouldn't bother making this point, if the immediately
preceding message hadn't been from someone whining because we changed
the behavior of hashname() ...)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Karayappalli, Raghunath (Raghu) | 2011-01-11 03:03:13 | database is growing... 1GB per day basis |
Previous Message | A.M. | 2011-01-10 23:51:27 | Using aclitem[] at application layer |