I second Edmund's comments: GlobalIDs have a few specific
purposes (which I personally try to avoid :)), but in the
discussion of SQLObject being specially aware / making
internal use of them, I'm opposed.
- Luke
Quoting Edmund Lian <el...@in...>:
>
> On 04/11/2003 01:47:59 PM Bud P.Bruegger wrote:
>
> >But what do you think of Globally Unique IDs?
>
> Seems unavoidable in certain situations--e.g.,
> implementing an access
> control mechanism where you want to grant/revoke rights
> to all sorts of
> data scattered across all sorts of tables in a consistent
> way. I've had to
> do this myself, and I use triggers and rules to
> generate/delete the global
> IDs.
>
> I've yet to see a need to have global IDs in any other
> situation though.
> Use of global IDs seems to arise mostly when one tries to
> force an RDBMS to
> behave like an object store.
>
> ...Edmund.
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Etnus, makers of
> TotalView, The debugger
> for complex code. Debugging C/C++ programs can leave you
> feeling lost and
> disoriented. TotalView can help you find your way.
> Available on major UNIX
> and Linux platforms. Try it free. www.etnus.com
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
>
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>
--
Many people are hamstrung by things like affection for
fellow employees, honesty, desire to appear to be a
"nice person," and other crippling limitations not
suffered by the truly powerful and successful.
|