> Hello Jerry and Martijn
>
> sets contains an iterator so you can iterate thru the objects
> also supports the contains method set.contains("new String("foo"))
> http://www.docjar.com/docs/api/java/util/Set.html
>
> Enums must use the exact index and are generally use for fixed constant
> Array
Mr. Shawn H. Corey wrote:
Actually, it's scarier to give access to people who know what they're
doing. They're the ones who would know how to sabotage it. Access
should only be granted to those who need it to do their jobs. Everyone
else should be restricted to using a user interface with pre
On Thu, 2008-07-31 at 11:47 -0500, Chris W wrote:
> My thought is you should develop an application that will give your
> users the information they need with out direct access to the DB. My
> thought is, if a user doesn't have a solid understanding of at least 1st
> and 2nd normal form, and ba
Jerry Schwartz wrote:
[JS] No, you've made several good points. My reasoning is that inexperienced
folks using this table through MS Access don't generally understand enough
about database design to create the necessary JOINs to do it right. Perhaps
the trade-off is a bad one.
My thought is
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Perrin
>Harkins
>Sent: Thursday, July 31, 2008 11:25 AM
>To: Jerry Schwartz
>Cc: mysql@lists.mysql.com
>Subject: Re: SET vs. ENUM
>
>On Thu, Jul 31, 2008 at 9:46 AM, Jerry Schwartz
><[EMAIL PROTECTED]&
>-Original Message-
>From: Martijn Tonies [mailto:[EMAIL PROTECTED]
>Sent: Thursday, July 31, 2008 10:32 AM
>To: mysql@lists.mysql.com
>Subject: Re: SET vs. ENUM
>
>Jerry,
>
>> >> Other than the fact that an ENUM can have many more values than a
>
On Thu, Jul 31, 2008 at 11:38 AM, Mr. Shawn H. Corey
<[EMAIL PROTECTED]> wrote:
> I don't see how that can be; with ENUM the DB has to set aside enough
> bytes for the longest identifier.
ENUMs are stored as integers.
> The only advantage of ENUM is that
> the data is in the same table; you don't
On Thu, 2008-07-31 at 11:24 -0400, Perrin Harkins wrote:
> On Thu, Jul 31, 2008 at 9:46 AM, Jerry Schwartz
> <[EMAIL PROTECTED]> wrote:
> > Other than the fact that an ENUM can have many more values than a SET, is
> > there any particular reason to choose one over the other?
>
> The only use for E
On Thu, Jul 31, 2008 at 9:46 AM, Jerry Schwartz
<[EMAIL PROTECTED]> wrote:
> Other than the fact that an ENUM can have many more values than a SET, is
> there any particular reason to choose one over the other?
The only use for ENUM is to make your data smaller. It offers no
protection against il
Jerry,
> >> Other than the fact that an ENUM can have many more values than a SET,
> >is
> >> there any particular reason to choose one over the other?
> >
> >Well, they are -different things- ...
> >
> >SETs shouldn't be used at all, IMO.
> >
> [JS] Why?
It goes against normalizing your data, th
>-Original Message-
>From: Martijn Tonies [mailto:[EMAIL PROTECTED]
>Sent: Thursday, July 31, 2008 9:51 AM
>To: mysql@lists.mysql.com
>Subject: Re: SET vs. ENUM
>
>Jerry,
>
>> Other than the fact that an ENUM can have many more values than a SET,
>is
Jerry,
> Other than the fact that an ENUM can have many more values than a SET, is
> there any particular reason to choose one over the other?
Well, they are -different things- ...
SETs shouldn't be used at all, IMO.
ENUM can be somewhat useful, I guess.
Martijn Tonies
Database Workbench - dev
Other than the fact that an ENUM can have many more values than a SET, is
there any particular reason to choose one over the other?
Regards,
Jerry Schwartz
The Infoshop by Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
<
13 matches
Mail list logo
