DLZ fields in database

Hello, I now have DLZ up and running on RHEL, it seems to be working  
well. I have a few questions, simple probably.

Is there any reason I can not mix file based zones as usual in named?   
I have a small handful of zones that will never change, and rather  
than run the risk of someone nuking out the entire database, I would  
like to keep those on disk.  Is this any issue?  I assume I just set  
up my keys and move on as usual?

Does named log as usual even though all the queries are coming out of  
a database?  So I can set up a query log, transfer log, and whatever  
other log breakdowns I want and those will work as normal?

Do I need to update the serial whenever a record changes? Any issue  
with just making it an in with an on update increment restraint on it?

Does case matter in any way as to what is stored in the database, so  
'a' or 'A' ?

Can I use non second values in the database such as 1D, 4H etc etc.

So far, this is looking like a perfect solution to my needs, thanks  
for making it available.
--
Scott * If you contact me off list replace talklists@ with scott@ *


------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com