Re: table design question

2015-07-29 Thread Richard Reina
Hi Peter, Thanks for the reply. So are you saying like this? Repair RID INT, Date DATE, Tech_ID INT, R_TYPE_ID INT 1 2015-07-28 3243 3 2 2015-06-15 1253 1 Repair_details ID, APL_TYPE VARCHAR(35), REPAIR_CODE CHAR(4), DESC 1 Refridgerator C

Re: table design question

2015-07-29 Thread shawn l.green
Hi Richard, On 7/29/2015 10:19 AM, Richard Reina wrote: If I were to create a database table(s) to tract most common repairs to different appliances I can't decide if it would be better to create one table with a long ENUM column that contains repairs that could be attributed to any appliance or

Re: table design question

2011-09-21 Thread Jan Steinman
> From: Richard Reina > > I want to create a US geography database. So far I have categories such as > state nick names (some states have more than one), state mottos (text 25 to > 150 characters), state name origins (100-300 characters), state "trivial > facts", entry into union. My question is

Re: table design question

2011-09-19 Thread Richard Reina
Thank you very much for all the insightful advice. I will keep the separated. 2011/9/19 Jerry Schwartz > >-Original Message- > >From: Richard Reina [mailto:gatorre...@gmail.com] > >Sent: Monday, September 19, 2011 9:55 AM > >To: mysql@lists.mysql.com > >Subject: table design question > >

Re: table design question

2011-09-19 Thread Johnny Withers
I would design three tables: Table1 (states): ID, name, abbreviation Table2 (state_item): ID, state_id (from states), item_id (from item_type), item_value (varchar) Table3 (item_type): ID, item_name Into the item_type table you can insert: Nick Name Motto Name origin Facts SomeOtherDataPoint S

RE: table design question

2011-09-19 Thread Jerry Schwartz
>-Original Message- >From: Richard Reina [mailto:gatorre...@gmail.com] >Sent: Monday, September 19, 2011 9:55 AM >To: mysql@lists.mysql.com >Subject: table design question > >I want to create a US geography database. So far I have categories such as >state nick names (some states have more

Re: Table design help

2010-09-09 Thread mos
At 04:23 PM 9/9/2010, Tompkins Neil wrote: Hi all, Needing some advice on my tables design. Basically I am designing a soccer application, and have a table which contains player_bids (the values of which a player costs to be transferred between clubs). Can someone please offer some input on th

Re: Table Design

2008-07-15 Thread John Hicks
Neil Tompkins wrote: Hi, I've the following table design (attached txt file, for some reason the content was being blocked) and I'd like any advice if this is the correct method/design. TableName:ProductMaster ProductMasterID FriendlyProductName TableName:ProductContent ProductContentID P

Re: Table Design

2008-04-25 Thread Sebastian Mendel
Krishna Chandra Prajapati schrieb: Hi All, Below is the table design on mysql server. CREATE TABLE `coupon_per_course` ( `coupon_id` int(10) unsigned NOT NULL default '0', `course_id` int(10) unsigned NOT NULL default '0', PRIMARY KEY (`coupon_id`,`course_id`), KEY `idx_coupon_per_cour

Re: Table Design

2008-04-24 Thread Krishna Chandra Prajapati
Hi wultsch, Thanks a lot. Every thing is going fine. I am only concerned with duplicate index, as it is using disk space. Is there any solution so that i can ignore duplicate index by altering the table design. OR i have to end up with duplicate index. Thanks, Krishna Chandra Prajapati On Thu,

Re: Table Design

2008-04-24 Thread Rob Wultsch
On Thu, Apr 24, 2008 at 6:40 AM, Krishna Chandra Prajapati <[EMAIL PROTECTED]> wrote: > Hi All, > > Below is the table design on mysql server. > > CREATE TABLE `coupon_per_course` ( > `coupon_id` int(10) unsigned NOT NULL default '0', > `course_id` int(10) unsigned NOT NULL default '0', > P

Re: Table design; 2-column index

2006-04-24 Thread Dan Nelson
In the last episode (Apr 24), Fan, Wellington said: > Thanks; I was really trying to ask about the potential performance > gain, however. I don't care so much about the UNIQUEness, but the > INDEXness. > > See, I am wondering if I create an 2-column index wiht fk1 as the > first component, will th

RE: Table design; 2-column index

2006-04-24 Thread Fan, Wellington
query? > -Original Message- > From: Dan Nelson [mailto:[EMAIL PROTECTED] > Sent: Monday, April 24, 2006 1:40 PM > To: Fan, Wellington > Cc: mysql@lists.mysql.com > Subject: Re: Table design; 2-column index > > > In the last episode (Apr 24), Fan, Wellin

Re: Table design; 2-column index

2006-04-24 Thread Dan Nelson
In the last episode (Apr 24), Fan, Wellington said: > If I have a table: > > CREATE TABLE t ( > id int(11) NOT NULL auto_increment, > fk1 mediumint(9) NOT NULL default '0', > fk2 smallint(6) NOT NULL default '0', > PRIMARY KEY (id), > UNIQUE KEY idxfk1 (fk1,fk2), > UNIQUE KEY idxfk2 (

Re: table design question

2004-01-29 Thread James M Moe
rmck wrote: I have "ip_address" and "ports" that I want to use in my table. I was just going to make each one a varchar. But was wondering if anyone has a better suggestion? Should I use int for "ports", which will have an index. Not sure how to store "ip_address". Use a varchar for the IP add

Re: table design question

2004-01-29 Thread Jochem van Dieten
Mark Matthews wrote: Jochem van Dieten wrote: rmck said: I have "ip_address" and "ports" that I want to use in my table. I was just going to make each one a varchar. But was wondering if anyone has a better suggestion? PostgreSQL ;-) It has a native datatype for storing IP addresses. That means th

Re: table design question

2004-01-29 Thread Mark Matthews
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jochem van Dieten wrote: > rmck said: > >>I have "ip_address" and "ports" that I want to use in my table. I >>was just going to make each one a varchar. But was wondering if >>anyone has a better suggestion? > > > PostgreSQL ;-) > > It has a native da

Re: table design question

2004-01-29 Thread Jochem van Dieten
rmck said: > I have "ip_address" and "ports" that I want to use in my table. I > was just going to make each one a varchar. But was wondering if > anyone has a better suggestion? PostgreSQL ;-) It has a native datatype for storing IP addresses. That means that things like sorting and subnet inclu

Re: Table design help

2003-10-29 Thread Reverend Deuce
Casey, I would consider, on the most basic level, a method like this: Contacts (all the company contact info, etc) using primary key contact_id -> IndustrialRelationships table <- industry_id primary key on Industries table (all the different type of industries) So, in the IndustrialRelationship

RE: Table design help

2003-10-29 Thread Dan Greene
you are going to want a 'buster' table... also known as a many-to-many table so you have: contacts Contact_Key Industries - Industry_Key Contact_Industry_assoc -- Contact_Key Industry_Key > -Original Message- > From: DeBerry, Casey [mailto:[EMAI

RE: Table design suggestions?

2003-06-12 Thread Damien COLA
This wouldn't work for a member belonging to several groups. 3 tables is the way to go. Cordialement, Damien COLA -Original Message- i'd set it up like this Table Group id int auto_increment name char Table Member userID int auto_increment name char groupID -- MySQL Gen

Re: Table design suggestions?

2003-06-11 Thread daniel
> Table Group > id int auto_increment > name char > > Table Member > groupID int auto_increment > name char > > Table Relationship > group_id int > member_id int > i'd set it up like this Table Group id int auto_increment name char Table Member userID int auto_increment name cha

Re: Table design suggestions?

2003-06-11 Thread danchik
given this, how would you write a query to list all members that are part of group_id=1 AND group_id=2 AND ... group_id 20. without having to write 20 "JOIN relationship r1 on r1.group_id =1 JOIN relationship r20 on r20.group_id =20) wich gets extremely slow with large ammounts of JOINS.

Re: Table design suggestions?

2003-06-11 Thread Michael Brunson
On Wed, 11 Jun 2003 22:17:09 -0230, "JJ" <[EMAIL PROTECTED]> wrote: [...] | *** | * The second idea is to create two tables. | *** | table groups | groupName varchar primary key | groupDescription text | | table groupRelations

Re: Table design suggestions?

2003-06-11 Thread Ryan Fox
On Wednesday 11 June 2003 08:47 pm, JJ wrote: > I have to add group functionality to an existing database. The > functionality required will be something like /etc/group in linux. How about 3 tables. Groups, Members, and Relationships. Table Group id int auto_increment name char Table Memb

Re: Table Design

2003-03-05 Thread gerald_clark
Band members should probably be in a separate table. One person may be a member of several bands, and the membership in a band changes over time. This will make modeling difficult. [EMAIL PROTECTED] wrote: Hello, I`m doing a database in MySQL to catalog cds, and i`m not sure if my table structure

RE: Table Design

2002-07-23 Thread Gordon
First of all, changing action to INT(2) vs INT(11) takes the same space {# inside ()'s is for display purposes not storage} on disk {I think it's 4 bytes, but would have to look it up}. TINYINT or maybe even ENUM {my preference} would only take 1 byte and would serve your purpose. You could make

Re: Table Design -- which is better?

2001-02-23 Thread Jason Landry
Have you considered using the SET datatype? It would be perfect for your situation. - Original Message - From: "Nino Skilj" <[EMAIL PROTECTED]> To: "'Tbone'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Friday, February 23, 2001 7:38

RE: Table Design -- which is better?

2001-02-23 Thread Atle Veka
- > From: Tbone [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 23, 2001 4:18 PM > To: [EMAIL PROTECTED] > Subject: Re: Table Design -- which is better? > > > Hi, > How would the data look a like. > And how about the query's > > Greetz Tbone > ---

RE: Table Design -- which is better?

2001-02-23 Thread Nino Skilj
The data would be 1's and 0's (on/off) Nino -Original Message- From: Tbone [mailto:[EMAIL PROTECTED]] Sent: Friday, February 23, 2001 4:18 PM To: [EMAIL PROTECTED] Subject: Re: Table Design -- which is better? Hi, How would the data look a like. And how about the query'

Re: Table Design -- which is better?

2001-02-23 Thread Tbone
Hi, How would the data look a like. And how about the query's Greetz Tbone - Original Message - From: "Nino Skilj" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, February 24, 2001 12:17 AM Subject: Table Design -- which is better? > I have a general design question. > > Is