Looking for some help / comments if possible ?
Cheers
Neil
-- Forwarded message --
From: Neil Tompkins neil.tompk...@googlemail.com
Date: Tue, Aug 31, 2010 at 8:48 PM
Subject: Database design help
To: mysql@lists.mysql.com
Hi
I've a soccer application consisting of managers
at 8:48 PM
Subject: Database design help
To: mysql@lists.mysql.com
Hi
I've a soccer application consisting of managers, teams players and
fixtures/results. Basically each manager will get points for each game
which
will depend on the result.
What would be the best table design bearing
: Tompkins Neil [mailto:neil.tompk...@googlemail.com]
Sent: 01 September 2010 12:52
To: [MySQL]
Subject: Fwd: Database design help
Looking for some help / comments if possible ?
Cheers
Neil
-- Forwarded message --
From: Neil Tompkins neil.tompk...@googlemail.com
Date: Tue, Aug 31, 2010
Tompkins [mailto:neil.tompk...@googlemail.com]
Sent: Tuesday, August 31, 2010 3:48 PM
To: mysql@lists.mysql.com
Subject: Database design help
Hi
I've a soccer application consisting of managers, teams players and
fixtures/results. Basically each manager will get points for each game
which will depend
site: www.the-infoshop.com
-Original Message-
From: Neil Tompkins [mailto:neil.tompk...@googlemail.com]
Sent: Tuesday, August 31, 2010 3:48 PM
To: mysql@lists.mysql.com
Subject: Database design help
Hi
I've a soccer application consisting of managers, teams players and
fixtures
E-mail: je...@gii.co.jp
Web site: www.the-infoshop.com
-Original Message-
From: Neil Tompkins [mailto:neil.tompk...@googlemail.com]
Sent: Tuesday, August 31, 2010 3:48 PM
To: mysql@lists.mysql.com
Subject: Database design help
Hi
I've a soccer application consisting of managers, teams
Hi
I've a soccer application consisting of managers, teams players and
fixtures/results. Basically each manager will get points for each game
which will depend on the result.
What would be the best table design bearing in mind that a manager can
move to a different club.
My thought was
Hello,
Currently, I have four tables (Items, UpdatePrice, UpdateStatus and
UpdateRelease). All the Update tables are linked to Items.ItemID via
Update(Price|Status|Release)ItemKey. Personally, I don't feel that
this is the best database design I could have, but I can't seem to
come up with one
pour le contenu fourni.
Date: Sat, 3 Oct 2009 18:11:59 -0600
From: john.l.me...@gmail.com
To: m...@phillipsmarketing.biz
CC: mysql@lists.mysql.com
Subject: Re: Questions on Database Design
Mark Phillips wrote:
On Sat, Oct 3, 2009 at 3:06 PM, Martin Gainty mgai...@hotmail.com
I am new at database design, and my question relates to the trade-offs
between putting all data in one database or several for mysql. For example,
say I have an application where a users login from their mobile phones and
read/write data to a database. Say there are roughly 10-15 tables
Mark Phillips wrote:
I am new at database design, and my question relates to the trade-offs
between putting all data in one database or several for mysql. For example,
say I have an application where a users login from their mobile phones and
read/write data to a database. Say there are roughly
On Sat, Oct 3, 2009 at 2:47 PM, John Meyer john.l.me...@gmail.com wrote:
Mark Phillips wrote:
I am new at database design, and my question relates to the trade-offs
between putting all data in one database or several for mysql. For
example,
say I have an application where a users login from
John,
Thanks. The data is private to each user; there is no sharing of data.
I am not sure what you mean by are the actions related Each user is
reading/writing independently of each other. Would that argue for
separate databases?
Mark
Are the actions of a similar nature (i.e. they're
a where userID=xxx clause?
Mark
Date: Sat, 3 Oct 2009 14:38:25 -0700
Subject: Questions on Database Design
From:
To: mysql@lists.mysql.com
I am new at database design, and my question relates to the trade-offs
between putting all data in one database or several for mysql
On Sat, Oct 3, 2009 at 4:02 PM, John Meyer john.l.me...@gmail.com wrote:
John,
Thanks. The data is private to each user; there is no sharing of data. I
am not sure what you mean by are the actions related Each user is
reading/writing independently of each other. Would that argue for
Mark Phillips wrote:
On Sat, Oct 3, 2009 at 3:06 PM, Martin Gainty mgai...@hotmail.com wrote:
depends on the relationship of the Data Tables and the Users that use them
for instance if I was to setup a table of outgoing calls from 2 distinct
individuals :
Me calls to
-Original Message-
From: AndrewJames [mailto:andrewhu...@gmail.com]
Sent: Saturday, September 12, 2009 1:20 AM
To: Kyong Kim; Arthur Fuller
Cc: Claudio Nanni; mysql
Subject: Re: database design
thank you all, i think
You probably wouldn't need Article_Type table if you're going to store
.
--
From: Kyong Kim kykim...@gmail.com
Sent: Saturday, September 12, 2009 8:22 AM
To: Arthur Fuller fuller.art...@gmail.com
Cc: Claudio Nanni claudio.na...@gmail.com; AndrewJames
andrewhu...@gmail.com; mysql mysql@lists.mysql.com
Subject: Re: database design
A) You would
le contenu fourni.
Date: Fri, 11 Sep 2009 15:22:57 -0700
Subject: Re: database design
From: kykim...@gmail.com
To: fuller.art...@gmail.com
CC: claudio.na...@gmail.com; andrewhu...@gmail.com; mysql@lists.mysql.com
A) You would probably want to populate the Article.Article_Type column
Storing it directly will cause problems when you want to add a new Article
Type. IMO it's better to have an ArticleTypes table (AutoIncrement) and
store its values in the ArticleTypeID column in the Articles table.
A.
On Sat, Sep 12, 2009 at 1:19 AM, AndrewJames andrewhu...@gmail.com wrote:
This is a bit of a long shot, but i really need some help and or directed to
the best reading resources.
as i begun building my database (as i went along), i now realise i have to
stop coding and sit back and design the database properly before i can go
on.
However i am still unable to wrap
A.J., It sounds good to me!
You can be a little confused but you did it well,
It seems you have all you need there.
A) Yes
B) select * from articles A left join article_types AT on A.article_type =
AT.article_types_id
Claudio
2009/9/11 AndrewJames andrewhu...@gmail.com
This is a bit of a
I agree with Claudio. You have your design correct. The only other thing you
need is the uid qualifier. Presumably you are using PHP or some other front
end to present your data. Your front end would request the user's name and
password, saving the uid in a variable and then issuing the select
A) You would probably want to populate the Article.Article_Type column
with Article_Type.ID. You probably wouldn't need Article_Type table if
you're going to store Article_Type value directly.
I would also consider the use of natural primary key vs surrogate
primary key. We've seen good results
fuller.art...@gmail.com
Cc: Claudio Nanni claudio.na...@gmail.com; AndrewJames
andrewhu...@gmail.com; mysql mysql@lists.mysql.com
Subject: Re: database design
A) You would probably want to populate the Article.Article_Type column
with Article_Type.ID. You probably wouldn't need Article_Type table
...@gmail.com
Sent: Friday, September 04, 2009 6:09 PM
Subject: RE: Database design - help
given the following table layouts
URLs: URL_ID (primary key for URL) URL_TEXT URL_CATEGORY URL_ID
(key which points to URL.URL_ID) CATEGORY_ID (key which points to
CATEGORY.CATEGORY_ID) SUBCATEGORY_ID
les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
From: bobsh...@ntlworld.com
To: mysql@lists.mysql.com
CC: john.l.me...@gmail.com
Subject: Re: Database design - help
Date: Fri, 4 Sep 2009 16:24:22
; mysql@lists.mysql.com
Cc: john.l.me...@gmail.com
Sent: Friday, September 04, 2009 6:09 PM
Subject: RE: Database design - help
given the following table layouts
URLs: URL_ID (primary key for URL) URL_TEXT URL_CATEGORY URL_ID
(key which points to URL.URL_ID) CATEGORY_ID (key which
be helpful to me.
cheers
- Original Message -
From: John Meyer john.l.me...@gmail.com
To: BobSharp bobsh...@ntlworld.com
Cc: mysql@lists.mysql.com
Sent: Monday, August 31, 2009 4:56 PM
Subject: Re: Database design - help
BobSharp wrote:
As a complete newbie in MySQL, I need a database
facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
From: bobsh...@ntlworld.com
To: mysql@lists.mysql.com
CC: john.l.me...@gmail.com
Subject: Re: Database design - help
Date: Fri, 4 Sep 2009 16:24:22 +0100
Hi
Thanks
As a complete newbie in MySQL, I need a database
to store URLs related to Tenpin Bowling.
There are several Categories ... Equipment Manufacturers, Organistations,
(UK) ProShops, (UK) Bowling Centres, Personal Websites, Misc., Coaching
Instructional websites, etc.
There will be some
BobSharp wrote:
As a complete newbie in MySQL, I need a database
to store URLs related to Tenpin Bowling.
There are several Categories ... Equipment Manufacturers,
Organistations, (UK) ProShops, (UK) Bowling Centres, Personal
Websites, Misc., Coaching Instructional websites, etc.
There
hi all,
after a little 'research' and consultation with friends, i come up with
these tables for my database project.
table Item(ItemID,warehouse,ShapeID,weight,category,description)
table Shape(ShapeID,physical shape)
table Dimension(DimensionID,dimension)
table
` (`title`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;
Thanks for any continued support.
From: John Meyer [EMAIL PROTECTED]
Date: Wed, 23 May 2007 07:28:23 -0600
To: mysql@lists.mysql.com
Subject: Re: Database design
Officelink wrote:
Hi everyone,
I¹m trying to set up
Hi everyone,
I¹m trying to set up a database with information that will be used in a
garment slideshow in flash.
The information to be included as part of the slideshow would be:
code, optional title, description, colours, sizes, garment image, fabric
swatch image
Each clothing item to be
Officelink wrote:
Hi everyone,
I¹m trying to set up a database with information that will be used in a
garment slideshow in flash.
The information to be included as part of the slideshow would be:
code, optional title, description, colours, sizes, garment image, fabric
swatch image
Each
.
- Original Message -
From: Officelink [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Wednesday, May 23, 2007 8:29 AM
Subject: Database design
Hi everyone,
I¹m trying to set up a database with information that will be used in a
garment slideshow in flash.
The information
,
Jerry Schwartz
Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
-Original Message-
From: ppywriw [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 16, 2006 11:54 AM
To: mysql@lists.mysql.com
Subject: database design help
Hiya
that created it could access it?
A very newbie question i know, but i am one, i'll admit it.
Any help would be apprectiated.
Thanks
John
--
View this message in context:
http://www.nabble.com/database-design-help-tf2832533.html#a7908028
Sent from the MySQL - General mailing list archive
a password field on
it so only the user that created it could access it?
A very newbie question i know, but i am one, i'll admit it.
Any help would be apprectiated.
Thanks
John
--
View this message in context:
http://www.nabble.com/database-design-help-tf2832533.html#a7908028
Sent from the MySQL
Hello,
I'm not very experienced with MySql and I'm building a website that deal with
user profiles. User profiles involves lists of preferences to choose from (for
example, your contry, your profession, etc.), so the user chooses from a
drop-down lists. The most natural solution for this is to
I want to design a database for lots of users. Each user will be
managing their own messages. Does it make sense to create a table
for each user after they've registered?
Or should I just create one MESSAGES table and store messages there
keyed off of their user_id?
If I create a table
I want to design a database for lots of users. Each user will be managing
their own messages. Does it make sense to create a table for each user after
they've registered?
Or should I just create one MESSAGES table and store messages there keyed off
of their user_id?
If I create a table for
: Database design question
I want to design a database for lots of users. Each user will be managing
their own messages. Does it make sense to create a table for each user
after they've registered?
Or should I just create one MESSAGES table and store messages there keyed
off of their user_id?
If I
referencing the destinating user as well.
-Original Message-
From: James Tu [mailto:[EMAIL PROTECTED]
Sent: Monday, August 07, 2006 1:56 PM
To: mysql@lists.mysql.com
Subject: Database design question
I want to design a database for lots of users. Each user will be
managing
their own
@lists.mysql.com
Sent: Monday, August 07, 2006 4:11 PM
Subject: Re: Database design question
Thanks everyone.
Now I feel confident that one table will be fine (Tripp's stat of
30 million records put me at ease :) ).
Cheers,
-James
On Aug 7, 2006, at 4:08 PM, John Meyer wrote:
One table,
USERS
?) and be sure that these queries are approximately O(log
N) rather than O(N) or worse. You will need to change your database design
to fit the queries that you'll be doing. O(log N) queries would generally
be characterized by the fields you're searching or sorting on being key
fields (i.e. MySQL
Hello,
we currently have a small database setup for affilates and visitor/leads. I
believe we have a one to many application, one affiliate can have several
visitor/leads but each visitor can only be assigned to one affiliate.
What I need to know if this the best design for this setup.
- Original Message -
From: Mike Blezien [EMAIL PROTECTED]
To: MySQL List mysql@lists.mysql.com
Sent: Friday, February 17, 2006 7:49 AM
Subject: Database design help
Hello,
we currently have a small database setup for affilates and visitor/leads.
I believe we have a one to many
OK, I think I got it now. Thanks for the additional info, that helps alot.
Rhino wrote:
- Original Message - From: Mike Blezien [EMAIL PROTECTED]
To: MySQL List mysql@lists.mysql.com
Sent: Friday, February 17, 2006 7:49 AM
Subject: Database design help
Hello,
we currently have
I am looking for a tool to integrate with mysql...I have tried DBDesigner
and would like to get my hands on software that is equivalent or better than
DBDesigner...any suggestions? FYI: I have had some problems with importing,
printing etc with DBDesigner...
Thanks in advance...
, 2006 9:53 AM
To: mysql@lists.mysql.com
Subject: Visual database design system
I am looking for a tool to integrate with mysql...I have tried DBDesigner
and would like to get my hands on software that is equivalent or better than
DBDesigner...any suggestions? FYI: I have had some problems
Adi,
We use Dezign from Datanamic. Not free, not expensive either.
PB
-
Adi wrote:
I am looking for a tool to integrate with mysql...I have tried DBDesigner
and would like to get my hands on software that is equivalent or better than
DBDesigner...any suggestions? FYI: I have had
Looked good, but does not suport MySQL 5 :( - cost is not really an
issue
On 2/3/06, Peter Brawley [EMAIL PROTECTED] wrote:
Adi,
We use Dezign from Datanamic. Not free, not expensive either.
PB
-
Adi wrote:
I am looking for a tool to integrate with mysql...I have tried
]
Sent: Friday, February 03, 2006 9:53 AM
To: mysql@lists.mysql.com
Subject: Visual database design system
I am looking for a tool to integrate with mysql...I have tried DBDesigner
and would like to get my hands on software that is equivalent or better
than
DBDesigner...any suggestions? FYI: I
At 10:52 AM -0500 2/3/06, Adi wrote:
I am looking for a tool to integrate with mysql...I have tried DBDesigner
and would like to get my hands on software that is equivalent or better than
DBDesigner...any suggestions? FYI: I have had some problems with importing,
printing etc with DBDesigner...
.
sales rep comission is relevante to the sales rep, but
not to the
transaction nor the product.
My point is, a database design can be a complex task, and the
hability an
application will have to provide solutions to the real world depends, before
anyother thing in that database
PROTECTED]
To: Marco Neves [EMAIL PROTECTED]; mysql@lists.mysql.com
Sent: Friday, January 20, 2006 3:49 PM
Subject: Re: Database design help
Marco,
Thanks for your help. I created this example to try to simplify my real
world problem. Clearly I didn't provide enough detail. Keeping with my
Neves [EMAIL PROTECTED]; mysql@lists.mysql.com
Sent: Friday, January 20, 2006 3:49 PM
Subject: Re: Database design help
Marco,
Thanks for your help. I created this example to try to simplify my real
world problem. Clearly I didn't provide enough detail. Keeping with my
example, essentially I'm
by a
disinterested third party; ignore it if you like
:-)
Rhino
- Original Message - From: Ian Klassen [EMAIL PROTECTED]
To: Marco Neves [EMAIL PROTECTED]; mysql@lists.mysql.com
Sent: Friday, January 20, 2006 3:49 PM
Subject: Re: Database design help
Marco,
Thanks for your help. I
- From: Ian Klassen [EMAIL PROTECTED]
To: Marco Neves [EMAIL PROTECTED]; mysql@lists.mysql.com
Sent: Friday, January 20, 2006 3:49 PM
Subject: Re: Database design help
Marco,
Thanks for your help. I created this example to try to simplify my real
world problem. Clearly I didn't provide enough
Hi all,
I'm trying to figure out a solution to the following problem.
Let's say I have a store with various products. I take inventory of these
products on different days. At any given time I want to view what the
inventory is for the entire store. I also want to know whether the
Hi,
Why don't you create two table:
* a product table, with the product discriptions, and other product
related
info (call it prod):
|ID|NAME|SOME|OTHER|FIELDS|
|1|ProdA|..|..|..|
|2|ProdB|..|..|..|
* a stock movements table, with moviments by
;
With this design, you won't have an inventory table of several hundred
columns and you won't need to change your database design every time a
product is added or removed from inventory.
Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine
At 06:27 PM 1/18/2006 +, Marco Neves wrote:
Hi,
Why don't you create two table:
* a product table, with the product discriptions, and other
product related
info (call it prod):
|ID|NAME|SOME|OTHER|FIELDS|
|1|ProdA|..|..|..|
|2|ProdB|..|..|..|
I built my inventory system like this,
I have a products table that contains all the information specific to each
part, less the quantity, i.e. Part Number, Description, Vendor, Color, Weight,
SKU number, etc...
Then I have another table that is my Inventory Tranactions Log that is just the
Thanks Ed. That's another good idea. The consensus I'm getting is to
create one table that stores unchanging data about the product and another
that stores transaction details. The
problem I'm still having is how to efficiently handle more than one
changing value.
As an example, let's say
point is, a database design can be a complex task, and the hability
an
application will have to provide solutions to the real world depends, before
anyother thing in that database design.
The is the point where almost all analisys most be done, and almost no
programming (i think
Hi,
I'm sure this is a stupid question, but I haven't been able to find
it myself. Surely there must be a free PHP utility to
web-administrate a MySQL database? I use CocoaMySQL
(http://cocoamysql.sourceforge.net/) on my own Mac, but it isn't
suitable for online databases. Can anyone lead me
@lists.mysql.com
Subject: MySQL database design documentation
Hi,
I'm sure this is a stupid question, but I haven't been able to find
it myself. Surely there must be a free PHP utility to
web-administrate a MySQL database? I use CocoaMySQL
(http://cocoamysql.sourceforge.net/) on my own Mac
I'm trying to think of the ways I can accomplish having a master
database of countries and states/provinces that I can reference in
several other databases.
I'd like to have a table of countries available for selection by the
users in a web app, but I'm not sure of the best way to then allow
Hi,
I'm relatively new to the database-scene. I've installed MySQL on Mac
OSX 10.3, which was easy. I've installed Perl support for MySQL,
which was suprisingly difficult. I've installed CocoaMySQL
(http://cocoamysql.sourceforge.net/) to create, inspect and backup
databases. And now I'm
- Original Message -
From: Maurice van Peursem [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Sunday, November 27, 2005 6:33 PM
Subject: MySQL database design documentation
Hi,
I'm relatively new to the database-scene. I've installed MySQL on Mac OSX
10.3, which was easy. I've
A couple of good links for databases.
Database Design (quick and dirty, but gets the points across):
http://www.geekgirls.com/menu_databases.htm - the from scratch side
SQL:
Basics: http://www.sqlcourse.com (you probably already know this stuff -
but just in case.
semi-Advanced: http
Relational Database Design Clearly Explained, Second Edition
ISBN: 1558608206
The original edition was my first primer on relational databases. It was
an excellent read.
Ben
Maurice van Peursem wrote:
Hi,
I'm relatively new to the database-scene. I've installed MySQL on Mac
OSX 10.3
Matthew Lenz wrote:
anyone using openoffice:base to design mysql db's? back when I tried it
earlier this year it wasn't able to define relationships which made it
pretty much useless as a time saving tool.
Hi Matt,
Although it's slightly OT here, there is still a lot of development
going on
anyone using openoffice:base to design mysql db's? back when I tried it
earlier this year it wasn't able to define relationships which made it
pretty much useless as a time saving tool.
-Matt
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
I need links about good database design information for high loaded web
sites...
regards, okan
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
I need links about good database design information for high loaded web
sites...
A database design should start with the logical data-related requirements,
not with performance related issues.
IMO, of course.
With regards,
Martijn Tonies
Database Workbench - tool for InterBase, Firebird
customers happy.
Tim Hayes
MYdbPAL - www.it-map.com
-Original Message-
From: Martijn Tonies [mailto:[EMAIL PROTECTED]
Sent: 22 September 2005 09:02
To: mysql@lists.mysql.com
Subject: Re: good database design
I need links about good database design information for high loaded web
Hi,
Please reply to the list and not to me personally only.
I want to explain my condition. I have a web site that habe 110onlne users
at same time. But cpu usage is 2.00/2.00 (p4 3.0ghzHT)
I think my database design is horrible because of this high cpu load.
Did you do an analysis to come
Hello Tim,
I disagree completely.
I prefer to have regard to the statement of requirement, which in this
case
is a concern over performance. If following conventional design rules
creates performance issues, then performance related issues come first
when
considering design.
Given that the
link, any info, any word is important
forme. I can't find the right start point.
Thanks
OKAN
- Original Message -
From: Martijn Tonies [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Thursday, September 22, 2005 11:25 AM
Subject: Re: good database design
Hi,
Please reply
Tim Hayes wrote:
I disagree completely.
I prefer to have regard to the statement of requirement, which in this case
is a concern over performance. If following conventional design rules
creates performance issues, then performance related issues come first when
considering design.
-
actually you should start worrying abt the DB Tuning and harware
requirements.
sujay
-Original Message-
From: Ian Sales (DBA) [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 22, 2005 2:17 PM
To: [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com
Subject: Re: good database design
Tim Hayes
This is an interesting subject area.
In a data warehousing environment, one tends to adopt table structures such
as snowflake layouts which lead to improved performance.
Createing a perfect normalised database design may well lead to performance
issues. The more joins you have, by far the worse
Martijn Tonies wrote:
Given that the OP did not state that there were any issues with an
existing website, logical requirements come first. Period. No discussion ;)
Logical requirements may come first, but may be overruled later by
requirements caused by performance issues or system
Hi,
Given that the OP did not state that there were any issues with an
existing website, logical requirements come first. Period. No discussion
;)
Logical requirements may come first, but may be overruled later by
requirements caused by performance issues or system limitations.
Which is
This is an interesting subject area.
In a data warehousing environment, one tends to adopt table structures
such
as snowflake layouts which lead to improved performance.
Createing a perfect normalised database design may well lead to
performance
issues.
If this is the case, go bug
: good database design
This is an interesting subject area.
In a data warehousing environment, one tends to adopt table structures
such
as snowflake layouts which lead to improved performance.
Createing a perfect normalised database design may well lead to
performance
issues
, September 22, 2005 2:17 PM
To: [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com
Subject: Re: good database design
Tim Hayes wrote:
I disagree completely.
I prefer to have regard to the statement of requirement, which in this
case is a concern over performance. If following conventional design
rules
, 2005 8:39 AM
To: 'rtroiana'
Subject: RE: Database design query
I know what you are trying to do and I can see the logic advantage of having
a single table that defines the the group relationship for users hosts and
groups. I just don't think the rules governing foreign keys will allow this.
Your
Hi All,
I'm trying to get data from Active Directory and storing in database. So I
have the following tables with their corresponding primary keys:
Group (GroupID)
Host (HostID)
User (UserID)
GroupMember(GroupID, MemberID)
The
Hi,
i think you must normalize your table to more than one table.
Users/Groups : N:1
Groups/Groups : N:1
Table Users :
User_id
Host
Group_id
Table Groups :
Group_id
Group_parent_id- is a another group_id
No data redondancy and robust implementation.
see for example /etc/passwd and
foreign key definitions on one field. If not
I think you are stuck with 3 tables instead of trying to do it in one.
-Original Message-
From: rtroiana [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 31, 2005 12:23 PM
To: mysql@lists.mysql.com
Subject: Database design query
Hi All,
I'm trying
I have four different activities. Each has its own set of data that
I want to save. So, I made four different tables to hold the saved
data. Each record also has 'keywords' field (essentially this is the
only field that all tables have in common.)
Later on, I want to search all the keywords
james tu [EMAIL PROTECTED] wrote on 04/26/2005 12:06:34 PM:
I have four different activities. Each has its own set of data that
I want to save. So, I made four different tables to hold the saved
data. Each record also has 'keywords' field (essentially this is the
only field that all
I tried that and maybe I'm doing something wrong but...
-I have to select the same number of columns...for each UNION
-And each of the records from the union fall under the same column
headings as the first SELECT...
I even tried to define column aliases..
SELECT `running` as `running_blah`...
If you posted your actual table structures (SHOW CREATE TABLE xx\G) I
think I could be more helpful. Right now I am just shooting in the dark.
Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine
James [EMAIL PROTECTED] wrote on 04/26/2005 02:15:49 PM:
I tried that and
I haven't created real project tables yet.
But here are the test ones that I'm experimenting with.
CREATE TABLE east (
id int(11) NOT NULL auto_increment,
keywords varchar(255) default NULL,
east_1 varchar(255) default NULL,
PRIMARY KEY (id)
) ;
CREATE TABLE north (
north_id int(11) NOT
1 - 100 of 233 matches
Mail list logo
