> yes this is the point. for sure it'd be better to use something else
> here -
> but there are certainly times when it would be nice to do atomic
> updates of
> sqlite dbs. without this ability you are bascially saying that, once
> a system
> goes into production you may never make big changes to the db without
> blocking
> all production readers/writers.
If you're making large changes to your system database
you really do not want to simply 'swap it in'. The system
should undergo testing and the service should be hot swapped in.
Create a backup of your service and test it. When you're
satisfied it works change the dns entries to point to the
new service. It's invisible to users and you have a backup
in case of problems, or a secondary copy you can use for
load sharing.
__________________________________
Do you Yahoo!?
Yahoo! Mail - 250MB free storage. Do more. Manage less.
http://info.mail.yahoo.com/mail_250
