Re: SQL design

2005-01-20 Thread pooly
Hello, I don't have any chance with this topic :-) I usually follow that list with my professional email, and there are often good advices on normalization or sql design. Do you need any more details ? Thanks for your help [EMAIL PROTECTED] écrit: > > Hello, > > I've

Re: SQL design/query question

2002-07-03 Thread Chris Griffin
late, I've not tested this code, and this is free > advice, > take it for what it's worth.) :) > > HTH, > =C+ > * > * Cal Evans > * The Virtual CIO > * http://www.calevans.com > * > > > -Original Message- > From: Chris Griffin [mailto:[EMAIL

RE: SQL design/query question

2002-07-02 Thread Cal Evans
The Virtual CIO * http://www.calevans.com * -Original Message- From: Chris Griffin [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 9:08 PM To: [EMAIL PROTECTED] Subject: SQL design/query question If this is not the right list for this please direct me to the proper list. I have

Re: SQL design/query question

2002-07-02 Thread Jed Verity
You need a LEFT JOIN. Read about it here: http://www.w3schools.com/sql/sql_join.asp Go down to the "LEFT JOIN" section. HTH, Jed I liked it when Chris Griffin wrote this to me: > If this is not the right list for this please direct me to the proper > list. > > I have a table of name/address

SQL design/query question

2002-07-02 Thread Chris Griffin
If this is not the right list for this please direct me to the proper list. I have a table of name/address information. I need to keep track of a weekly event and if they participated or not. I thought I could have a table of dates and people record ids with just those that participated. The

Quick SQL design help

2002-02-13 Thread James Carrier
Hello MySQL users I was wondering if one of you could advise me on the best solution to a problem I'm having - I'm sure this has been done before but haven't found anything in the archives. Basically the problem I am having is how best to handle multiple values for a specific column, in this cas

Fwd: Re: Quick SQL design help

2002-02-12 Thread tj marlin
>Date: Sun, 10 Feb 2002 16:06:55 -0800 >To: [EMAIL PROTECTED] >From: tj marlin <[EMAIL PROTECTED]> >Subject: Re: Quick SQL design help > >the SET data type comes to mind. there is a limitation of 64 for the set >size. > >ciao > >At 05:23 AM 2/10/02 +

Re: Quick SQL design help

2002-02-12 Thread DL Neil
Hello James, > Basically the problem I am having is how best to handle multiple values for > a specific column, in this case the values in question are coming from an > HTML SELECT MULTI box processed by PHP. > > The way I have been doing this so far is to have a delimited value stored > in a var

Re: Quick SQL design help

2002-02-12 Thread Amer Neely
> Hello MySQL users > > I was wondering if one of you could advise me on the best solution to a > problem I'm having - I'm sure this has been done before but haven't found > anything in the archives. > > Basically the problem I am having is how best to handle multiple values for > a specific col

Another question - Re: Quick SQL design help

2002-02-12 Thread James Carrier
Hi Amer Thanks for replying - I wonder if you could clear up a point for me. I'm going to have many, many possible multi values - too many for a SET or ENUM column as some other people have suggested. I'm happy using the following tables: parts (partid int, partname varchar(255)) cat

Re: Another question - Re: Quick SQL design help

2002-02-11 Thread Amer Neely
James Carrier wrote: > > Hi Amer > > Thanks for replying - I wonder if you could clear up a point for me. > I'm going to have many, many possible multi values - too many for a SET or > ENUM column as some other people have suggested. > I'm happy using the following tables: > > parts (

Re: Quick SQL design help

2002-02-10 Thread Amer Neely
> Hello MySQL users > > I was wondering if one of you could advise me on the best solution to a > problem I'm having - I'm sure this has been done before but haven't found > anything in the archives. > > Basically the problem I am having is how best to handle multiple values for > a specific col

Fwd: Re: Quick SQL design help

2002-02-10 Thread tj marlin
>Date: Sun, 10 Feb 2002 16:06:55 -0800 >To: [EMAIL PROTECTED] >From: tj marlin <[EMAIL PROTECTED]> >Subject: Re: Quick SQL design help > >the SET data type comes to mind. there is a limitation of 64 for the set >size. > >ciao > >At 05:23 AM 2/10/02 +

Re: Quick SQL design help

2002-02-10 Thread DL Neil
Hello James, > Basically the problem I am having is how best to handle multiple values for > a specific column, in this case the values in question are coming from an > HTML SELECT MULTI box processed by PHP. > > The way I have been doing this so far is to have a delimited value stored > in a var

Quick SQL design help

2002-02-09 Thread James Carrier
Hello MySQL users I was wondering if one of you could advise me on the best solution to a problem I'm having - I'm sure this has been done before but haven't found anything in the archives. Basically the problem I am having is how best to handle multiple values for a specific column, in this cas

RE: SQL/Design -- how to use sub entities/type discriminators ?

2002-01-14 Thread Rick Emery
7; Subject: FW: SQL/Design -- how to use sub entities/type discriminators ? You don't really have to do the two searches and if-then-else. You can use joins to first get all grads, then a join to get all profs. SELECT user.*,graduser.* FROM graduser LEFT JOIN user USING(userid); SELECT

FW: SQL/Design -- how to use sub entities/type discriminators ?

2002-01-14 Thread Rick Emery
ERIDs are unique among grads and profs magic words: mysql,database -Original Message- From: j.random.programmer [mailto:[EMAIL PROTECTED]] Sent: Monday, January 14, 2002 2:56 PM To: [EMAIL PROTECTED] Subject: SQL/Design -- how to use sub entities/type discriminators ? Hi all: Consi

RE: SQL/Design -- how to use sub entities/type discriminators ?

2002-01-14 Thread Rick Emery
ERIDs are unique among grads and profs -Original Message- From: j.random.programmer [mailto:[EMAIL PROTECTED]] Sent: Monday, January 14, 2002 2:56 PM To: [EMAIL PROTECTED] Subject: SQL/Design -- how to use sub entities/type discriminators ? Hi all: Consider a hierarchy of users. All users

SQL/Design -- how to use sub entities/type discriminators ?

2002-01-14 Thread j.random.programmer
Hi all: Consider a hierarchy of users. All users have certain properties (they all have a name and date-of-birth). Additionally, based on their type, users have more properties. So a graduate user may have information regarding the year and school of graduation, a professor user may have informa