: Mogens Melander [mailto:[EMAIL PROTECTED]
Sent: Monday, July 02, 2007 3:45 PM
To: mysql@lists.mysql.com
Subject: Re: database structure
On Mon, July 2, 2007 21:10, Hiep Nguyen wrote:
take your advice, i looked in to JOIN and i got the idea. but i noticed
that in order to use JOIN, don't you
for all your helps
T. Hiep
-Original Message-
From: Mogens Melander [mailto:[EMAIL PROTECTED]
Sent: Monday, July 02, 2007 3:45 PM
To: mysql@lists.mysql.com
Subject: Re: database structure
On Mon, July 2, 2007 21:10, Hiep Nguyen wrote:
take your advice, i looked in to JOIN and i got
Hi,
You can do this in four tables:
1. Tag
2. Shape (with an additional field, let us call it X, describing how
many data elements each shape has)
3. ShapeElements : one record describing each data element (length,
width etc.) for each shape. Record count for each shape: X
4. Data Table : X
Or:
Tag
ShapeDimension (type enum('height', 'thickness', etc), value VARCHAR()
or INT())
TagsShapeDimensions (FOREIGN KeY TAG, FOREIGN KEY ShapeDimension)
1 less table
Greetz,
boro
Rajesh Mehrotra schreef:
Hi,
You can do this in four tables:
1. Tag
2. Shape (with an additional field,
On Mon, 2 Jul 2007, Rajesh Mehrotra wrote:
Hi,
You can do this in four tables:
1. Tag
2. Shape (with an additional field, let us call it X, describing how
many data elements each shape has)
3. ShapeElements : one record describing each data element (length,
width etc.) for each shape. Record
On Mon, 2 Jul 2007, Borokov Smith wrote:
Or:
Tag
ShapeDimension (type enum('height', 'thickness', etc), value VARCHAR() or
INT())
TagsShapeDimensions (FOREIGN KeY TAG, FOREIGN KEY ShapeDimension)
1 less table
Greetz,
boro
Rajesh Mehrotra schreef:
Hi,
You can do this in four tables:
1.
CREATE TABLE `tags` (`tagid` INT(11) UNSIGNED AUTO_INCREMENT PRIMARY
KEY, `location` VARCHAR(255) NOT NULL DEFAULT '') ENGINE=INNODB;
CREATE TABLE `dimension_type` (`id` ..., `type` VARCHAR(255) NOT NULL
DEFAULT '') ENGINE=INNODB;
CREATE TABLE `tags_shape_dimensions` (`tag` INT(11) UNSIGNED,
On Mon, 2 Jul 2007, Christophe Gregoir wrote:
CREATE TABLE `tags` (`tagid` INT(11) UNSIGNED AUTO_INCREMENT PRIMARY KEY,
`location` VARCHAR(255) NOT NULL DEFAULT '') ENGINE=INNODB;
CREATE TABLE `dimension_type` (`id` ..., `type` VARCHAR(255) NOT NULL DEFAULT
'') ENGINE=INNODB;
CREATE TABLE
On Mon, July 2, 2007 21:10, Hiep Nguyen wrote:
take your advice, i looked in to JOIN and i got the idea. but i noticed
that in order to use JOIN, don't you need to have the same column name in
both tables? i just don't see it in your example here. is there
something that i'm missing?
bruce wrote:
hi...
i'm considering an app where i'm going to parse a lot of colleges (~1000)
faculty information. would it be better to have all the faculty information
in one large table or would it be better/faster to essentially place each
college in it's own separate table, and reference
You may want to look into normalization to keep
everything organized. However if you want pure query
speed, you will have to de-normalize some of your
tables to get optimum speed.
Have a look here for info on normalization:
http://databases.about.com/od/specificproducts/a/normalization.htm
HTH
bruce wrote:
hi...
i'm considering an app where i'm going to parse a lot of colleges (~1000)
faculty information. would it be better to have all the faculty information
in one large table or would it be better/faster to essentially place each
college in it's own separate table, and reference
@lists.mysql.com
Subject: Re: database structure question...
bruce wrote:
hi...
i'm considering an app where i'm going to parse a lot of colleges (~1000)
faculty information. would it be better to have all the faculty information
in one large table or would it be better/faster to essentially place each
I would strongly recommend creating one table, with a column that stores
the college_ID for each faculty member, and a separate table to
correlate college name and college_id. For example...
Create table faculty (
last_name varchar(50),
first_name varchar(50),
[mailto:[EMAIL PROTECTED]
Sent: Thursday, July 07, 2005 6:07 PM
To: [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com
Subject: Re: database structure question...
I would strongly recommend creating one table, with a column that stores
the college_ID for each faculty member, and a separate table
bruce wrote:
even though this might mean i get a table with 5 million records??? as
opposed to say a 1000 different tables, each with 50,000 records?
-bruce
That's right.
Databases are made for this sort of thing.
If you have a separate table for each location, constructing queries to
pull
You have not said what type of information you will be storing in this
database. Is it going to be just faculty information? Even if it is
just faculty information, you do realize that each school treats
departments a bit dfferently. The faculyt maybe under different
school, may specialize in
Where did you read that 25 million records would be a problem? I've
heard of people with billions of records in one table. The only
question would be performance, but indexes would largely take care of
that. You may run into issues with the physical size of the table and
the underlying OS not
PROTECTED]
Subject: Re: Database structure
Where did you read that 25 million records would be a problem? I've
heard of people with billions of records in one table. The only
question would be performance, but indexes would largely take care of
that. You may run into issues with the physical
I used to program for a medical tester.
I used method 2:
2 - a table with 60 rows for one assessment :
results(#assessment_nr, labtest_nr, p, d) where p and d are my two
results.
The BIG advantage was changes to the tests, adding new ones, or deleting
fields. Made it much more flexible.
The schema is :
Patients(#patient_nr,name,etc...)
Assessment(#assessment_nr, #patient_nr, assessment_type, other usefull
values).
Assessment_types(assessment_type, labtest_nr)
An assessment is composed of different tests, let's say assessment type 1
is
composed of lab test 1,2,3,5 and
Stephanie,
Does anyone know if there's a way in MySQL have the same functionality
without installing the whole program on a users machine? I'm using a Java
program along with Connector/J and a MySQL DB. We are trying to make it so
the user doesn't have to install MySQL everytime they want
Stephanie,
Connector/J takes advantage of client/server architecture over TCP. This
means that the MySQL server could exist on one machine (a server), and
the client application(s) can connect to it via TCP and Connector/J from
anywhere that has a TCP route to the MySQL server.
If Connector/J
Stephanie,
Without knowing the architecture of your program I cannot give a precise
answer. But I'll make a few stabs at it...
First, MySQL, being an application in its own right, can be installed
separately from your application. Alternately, your application's
installation program could
How are you connecting to MySQL?, through MySQL ODBC I
am assuming. I might happen that the ODBC driver for
MySQL does not implement ADOX functionality.
Have you tried to take a look to the MySQL++ API? You
might have to create your own dll (or COM component)
to modify the database structure
Yes. You want to use mysqldump.
http://www.mysql.com/doc/m/y/mysqldump.html
On Sun, 24 Feb 2002 22:24:39 -0500, Pax wrote:
Is there an easy way to create SQL script from existing database and use
it to create a new database?
Tks
Pax
Yes.. Use the DUMP command
-Original Message-
From: Pax [mailto:[EMAIL PROTECTED]]
Sent: Sunday, February 24, 2002 9:25 PM
To: 'MySQL'
Subject: database structure script
Is there an easy way to create SQL script from existing database and use
it to create a new database?
Tks
Pax
I should have been more clear...
http://www.mysql.com/doc/m/y/mysqldump.html
-Original Message-
From: Todd Williamsen [mailto:[EMAIL PROTECTED]]
Sent: Sunday, February 24, 2002 10:03 PM
To: 'Pax'; 'MySQL'
Subject: RE: database structure script
Yes.. Use the DUMP command
I'm not sure what you mean by "structural changes".
If the the two table have the same number of columns and they are in the same order,
you can do something like what I have explained below. It you included the table info
from prod and test I could help you better (DESC prod;).
# Create
clearer.
Cal
http://www.calevans.com
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Sunday, January 21, 2001 1:48 PM
To: Cal Evans
Cc: [EMAIL PROTECTED]
Subject: Re: Database structure DIFF
I'm not sure what you mean by "structural ch
eyeballing it...I'm just too lazy. :)
Thanks for replying. Hope I've made things clearer.
Cal
http://www.calevans.com
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Sunday, January 21, 2001 1:48 PM
To: Cal Evans
Cc: [EMAIL PROTECTED]
Subject: Re
31 matches
Mail list logo
