----- Original Message Excerpt ---
Dave wrote:
....
The logic is simple, but it is not as you describe. Currently, it is this: * If DB connection fails forward to DatabaseError action * Else if Roller tables not found direct to CreateDatabase action * Else if Roller tables need upgrade direct to UpgradeDatabase action I like your idea of having one central install action instead of routing logic in the filter.
Once all of these have passed at least once in a given instance of the process, we should be able to retain state to avoid repeating at least the latter two checks each time.
I don't know whether actually testing the connection each time is worthwhile.
--a.
