|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Alex K (spaceoutlet
gmail.com)
Date: Fri Jan 18 2008 - 11:30:10 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Kevin,
Well the basic information, company description and personalized
options will be selected many times (whenever a user submits a query).
It will basically be show on the result page of the search engine.
The user's login / password well is used to login, then the user may
update the company basic information, description and personalized
options. These updates may happen sporadically though. Once every 3
minutes these fields are selected again in order to update the search
engine index.
Thank you,
Alex
On 18/01/2008, Kevin Hunter <hunteke
earlham.edu> wrote:
> At 11:44a -0500 on 18 Jan 2008, Alex K wrote:
> > To summarize one table vs. many tables with one to one relations?
>
> As per usual, it depends on your needs. For most flexibility, and to
> give the DB the best chance to give the best plan for the possible
> requests I might make in the future, I generally tend towards
> normalization, not denormalization.
>
> The question is: what do you want to do with the schema?
>
> Kevin
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=alex.ksikes
gmail.com
>
>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]