------=_Part_15516_22796996.1153893971001
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi I am trying to make more efficient use of the tables that I have, since
the size seems to keep growing larger. I had my table fields to be all NOT
NULL and hence i never had to do any checking, now I am planning on using
this feature and allowing null fields in the tables. How would this affect
my fetching row values? how can I handle this? Also do you really think i
would be able to save anything with null? 90% of my fields are varchar(X) so
if they dont have a value they will only consume 1 byte of space, so then
would it make sense for me to make the fields null?

Thanks a ton
Ankur

------=_Part_15516_22796996.1153893971001--

------=_Part_107988_423217.1153924780225
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Actually, if you are using SSQL you will have to apply the patch, and if you
are using them, the actual eficiency of NULL fields are a matter of design
of the program and/or the database structure..

If you are using template queries, I do it in a student's management program
i am developing, you will find them more than usefull, if not sure you can
see the MySQL Manual to look for better use of

2006/7/26, Ankur G35 Saxena <g35rider (AT) gmail (DOT) com>:

--
Carlos Flores

------=_Part_107988_423217.1153924780225--