> Create composite index on (cat, date). Use EXPLAIN to see if MySQL uses
index:
> http://dev.mysql.com/doc/mysql/en/EXPLAIN.html
This partially solved my problem. Thanks a lot. However I am facing a new
problem here.
The query where I am ordering by a column is much more slowly than the same
que
Hi there,
I've been trying around for some time now and i just don't see a solution to
my problem:
I have a table called "feiertage" ("Holidays"):;
mysql> select * from feiertage;explain feiertage;
++
| datum |
++
| 2001-12-24 |
| 2001-12-25 |
| 2001-12-26 |
| 2002-0
Just my opinion, but I prefer numeric keys that the users *can't*
see, to alpha keys that the users can see:
1. numeric keys are faster
2. using numeric keys that the user can't see allows you
to open up(for UPDATE) ALL the fields that the user can see
including a field like School N
Think of the tables in your database as linked sets.
I have a college database where school description as info associated
in three other tables, allowing one school description, one or more
contacts, requirements for one or more programs, and each program has
one or more degrees associated, i
Hello,
I tend to do either what Hardy suggested depending on the needs of your
database. If the trouble ticket table is to be associated with both
faculty and staff, and that fac/staff can have more than one trouble
ticket I like to create a relational table.
To do this you create a separate ta
Try going to www.mysql.com and search for "foreign key" in the
search box - I found 28 matches - here are the 1st 3 matches:
1. MySQL Manual | 5.4.5 Foreign Keys [4]
2. MySQL Manual | 5.4.5.1 Reasons NOT to Use Foreign Keys constraints [4]
3. MySQL Manual | 9.3.6 Using Foreign Keys [4]
make sure
that no bad data gets put in them though.
Cal
http://www.calevans.com
-Original Message-
From: Chris Toth [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 05, 2001 9:56 AM
To: MySQL List
Subject: need some help here...
I'm having a extremely hard time grasping the
I'm having a extremely hard time grasping the concept of multiple tables. So
far, I've been using just one table when designing a database. But now I
have to design a database for a trouble-ticket system for our department.
I've written out the design of the tables, but the part I don't understa
