On Fri, Nov 28, 2008 at 5:52 PM, Fergus Gibson [EMAIL PROTECTED] wrote:
On Thu, Nov 27, 2008 at 11:19 AM, Bastien Koert [EMAIL PROTECTED] wrote:
2. It is possible to use the application to handle the keys instead of
the
database, it involves more work around key checking / validation before
On Thu, Nov 27, 2008 at 11:19 AM, Bastien Koert [EMAIL PROTECTED] wrote:
2. It is possible to use the application to handle the keys instead of the
database, it involves more work around key checking / validation before
creating or updating records, but it can be done if the INNODB table type
This is solved by using FOREIGN KEY but I'm not sure if MySQL have them
present or just planned for some future release.
mrfroasty napsal(a):
I am quite new to database designs, I have a problem in my design...I
can actually feel it, but I am not quite sure if there is a feature in
mysql or I
maruti wrote:
hey lemme knoe, how many columns are you planning for?
y not put table B columns in table A??
if you are least bothered about data normalizations, simply go the way
you want to.
userId Name Age Age Sex Occupation Location
all the data which has correspondence with userid can
danaketh wrote:
This is solved by using FOREIGN KEY but I'm not sure if MySQL have
them present or just planned for some future release.
mrfroasty napsal(a):
I am quite new to database designs, I have a problem in my design...I
can actually feel it, but I am not quite sure if there is a
Mr. Froasty,
From your note, it sounds like you want to use foreign keys; as Daniel
pointed out. I think an example would be helpful here. The subject of
foreign keys is bigger than a bread box so I'll just touch on the pieces
I think you'll find helpful. There is all sorts of literature
On Thu, Nov 27, 2008 at 1:36 PM, Fortuno, Adam
[EMAIL PROTECTED]wrote:
Mr. Froasty,
From your note, it sounds like you want to use foreign keys; as Daniel
pointed out. I think an example would be helpful here. The subject of
foreign keys is bigger than a bread box so I'll just touch on the
