ls.
>
> PB
>
> Original Message
> From: "Richard Reina"
> Reply-To: "Richard Reina"
> Date: 07/29/15 10:19 AM
> To: "mysql@lists.mysql.com"
> Cc:
> Sub: table design question
> If I were to create a database table(s) to tract most
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
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 different repair tables for each appliance.
All the tables
> 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
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
> >
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
>-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 name
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; would it be better to keep at
le
Hi,
I'm creating a application which hosts football matches and I want to record
the player appearances, goals etc. I was thinking of having a record for
each player as follows :
appearance_id
season_id
player_id
team_id
competition_id
appearance
goals
yellow_card
red_card
date_played
Is this t
Hi,
A very simple question. I have two products at our
website and i would like to keep track of how many of
each softwares were downloaded daily.
I am planning to create the following table:
id - auto_incr
date_of_download - data
product_name - enum value containing the two products
Then I pla
Mark Sargent <[EMAIL PROTECTED]> wrote on 06/03/2005 03:04:23 AM:
> Hi All,
> I'm not sure the best design approach for a product table for a number
> of different hardware devices. Some devices have IP, Port, CPU, Memory
> specs, whilst some don't. Current desing is below.
> Products:
> product
Hi All,
I'm not sure the best design approach for a product table for a number
of different hardware devices. Some devices have IP, Port, CPU, Memory
specs, whilst some don't. Current desing is below.
Products:
product_id
product_name
maker_id
controller_id
product_type_id
product_model_numbe
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
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
-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
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
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".
This table has the possibility of having
17 matches
Mail list logo
