Hi José,

>> The benefits of normalizing increase with the amount and/or  
>> complexity of your data. Notice there are no case statements to get  
>> what you want. You just start with the table you want (Split, in  
>> this case) and join any needed related data, so SQLite only scans  
>> the relevant data, rather than testing every row.
>
> Wouldn't this take longer to process then a case statement?

I wouldn't think so, no. This method (ie normalizing first) means that  
all the rows that have a "Split" value are already in one small table.  
So there's no searching through all the rows in the one huge table  
that's filled mainly with nulls. The joining with the Fund and Invoice  
data is done via the indexed primary key fields, a procedure for which  
SQL database engines are optimized.

In short, if you read the first chapter of any book on SQL  
programming, you'll see that normalizing your database is the  
fundamental first step in achieving the nest results with minimum  
wastage.

Tom
BareFeet

  --
5000 computer accessories delivered anywhere in Australia:
http://www.tandb.com.au/forsale/?ml
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to