Re: Design decision

2007-10-03 Thread Brent Baisley
I'm not sure why you say 30 or more inserts will take too long. As long as you do a bulk insert, it's just a single command. 30 individual insert will take it's toll. You are really looking for a logging system. Your not going to be querying the table all that much, just a lot of inserts. S

Re: Design decision

2007-10-03 Thread Chris
Scott Haneda wrote: Scott Haneda wrote: I have an a table of objects, attached to those objects are keywords. Users submit the keywords to the objects. Currently, I chose to keep a hit count on the keywords, so if a duplicate keyword is supplied, a counter is incremented. I thought this was a

Re: Design decision

2007-10-03 Thread Scott Haneda
> Scott Haneda wrote: >> I have an a table of objects, attached to those objects are keywords. >> Users submit the keywords to the objects. >> >> Currently, I chose to keep a hit count on the keywords, so if a duplicate >> keyword is supplied, a counter is incremented. >> >> I thought this was a

Re: Design decision

2007-10-03 Thread Chris
Scott Haneda wrote: I have an a table of objects, attached to those objects are keywords. Users submit the keywords to the objects. Currently, I chose to keep a hit count on the keywords, so if a duplicate keyword is supplied, a counter is incremented. I thought this was a good idea, as it keep

RE: Design decision

2003-07-28 Thread csebe
> From: Lin Yu [mailto:[EMAIL PROTECTED] > Sent: Monday, July 28, 2003 9:33 PM > To: [EMAIL PROTECTED]; 'mysqllist' > Subject: RE: Design decision > > > Lian, > > Between your design solutions (1) and (3), you need to decide, > from the logical > business

RE: Design decision

2003-07-28 Thread Lin Yu
Lian, Between your design solutions (1) and (3), you need to decide, from the logical business requirement, whether the nature of the relationship between user and group is one-to-many (a group may have many users, and each user may belong to exactly one group) or many-to-many (a group may have ma

Re: Design decision on generating data

2002-04-12 Thread Steven Hajducko
Usually I build my queries dynamically. I store all the values into a hash ( this is in perl mind you.. ) Then do something like this.. my (@fields, @vals); my ($field_str, $val_str); foreach $field_name (keys %hash) { if ($hash{$field_name}) { push @fields, $fie

Re: Design decision on generating data

2002-04-12 Thread Carl Schmidt
Thank you for the information. Let me please clarify that i am using a web form. I tried the one solution of converting those values that are not set to null, but mysql complained: SQL: INSERT INTO Development_Event_Show(showID,venueID,description,ageCutoff,ageDelimiter,price1,price2) VALU

Re: Design decision on generating data

2002-04-12 Thread Christopher Thompson
On Friday 12 April 2002 8:10 pm, Carl Schmidt wrote: > I have a form where a user enters some numbers into text boxes. Some of > the text boxes can be left blank. The business logic receives all > variables to all text boxes. Should I : I'm assuming that you are using an executable file and NO