On Thu, 10 Aug 2006, Thomas Bruederli wrote:
Eric Stadtherr wrote:
Should rev306 be backed out then? It goes against this concept.
Well, my explanations haven't been clear enough when I talked to Tobias... I'll take care of that, but it definitely goes against my ideas.
I don't see any reason to have lots of fields in the database if we choose a format that can be parsed fast and allows us interchange the data with other formats for import/export/sync. If searching the contacts gets a problem I suggest to create a fulltext index with all field values required for search.
I see two problems here:
- Anyone working on DB design would have stomach aches seeing it. :-)
Raelly, the problem could raise later because of the non-normalize database design. 2) Not all the database engines have good full text search indexes, and they tend to consume more resources.
I personally think that if we are gonna put and get data without searching, maybe it can all go in one field. Else, it makes it dificult to make the searches, and even worst, at the PHP side it's dificult to look for words in diferent sectors of the text field.
If you put it all in one text field, you'll have real headaches in the future. Trust me on this. ;-)
-- 21:50:04 up 2 days, 9:07, 0 users, load average: 0.92, 0.37, 0.18
Lic. Martín Marqués | SELECT 'mmarques' || Centro de Telemática | '@' || 'unl.edu.ar'; Universidad Nacional | DBA, Programador, del Litoral | Administrador