If, if and when it is possible. What I say is that they should come true on numerical fields and avoiding more of 1 for table, this is possible with a good design of the database.
I carry a lot of years (more of 16) accomplishing base designings of data and I have it more than proven. And of something he can be sure and it is that I do not violate the rules of integrity and normalization. Best Regards ========= || ISMAEL || ========= ----- Original Message ----- From: Norman Dunbar To: [email protected] Sent: Thursday, August 11, 2011 11:50 AM Subject: Re: [firebird-support] Re: Stumped on SQL Indexing/Bad Plan-ing On 11/08/11 16:27, Ismael L. Donis Garcia wrote: > The join you should always avoid them, > ... > this not only you should apply it in firebird > but in all the systems of SQL that you use. I'm not sure I follow what you are saying, avoid joins? In a relational database? Relational databases are built to perform joins, that's basically the point, you design the database, normalising your data into separate entities (which become tables) and when you run a query, you join these various tables back together as required for that particular query. Some data warehouse systems do advocate de-normalisation, but that's different from normal running of an RDBMS. (Plus, denormalisation has been proven to reduce response times.) Of course, I might have misunderstood your original posting. In which case, apologies. Cheers, Norm. -- Norman Dunbar Dunbar IT Consultants Ltd Registered address: Thorpe House 61 Richardshaw Lane Pudsey West Yorkshire United Kingdom LS28 7EL Company Number: 05132767 [Non-text portions of this message have been removed]
