i don't know if you just don't *want* to understand me or what's the problem.

in my first post in this thread i said "if there will be many searches".

*if*. i just said if. and i said, normalization can lead to worse performance. in case you didn't get it, the word 'can' is in italic. that statement is true and in my context it was not useless.

so all i did was pointing out that if the problem is, that the application has many searches, and normalization here would be worse for these searches, then one should consider a search engine to do the searches. i'm not that stupid to suggest to replace a database with a search engine.

i never said "don't normalize because it make things slow" or something like that.

i'm saying all that because i was working on code with a very flat database. it should have been normalized. but the database design was good for the searches, because almost all of the fields would be needed in a search. so what did we do in the end? replace database searches with a search engine. and that was a good decision. because then we were free to normalize without being worried.

In reply to Re^5: (OT) Couple of Data Model Design Considerations by tinita
in thread (OT) Couple of Data Model Design Considerations by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.