|Subject||Re: [firebird-support] Looking for some suggestions...Vertical market apps|
> On 02-Aug-2004 08:01:39, Lester Caine wrote:Actually now that I think of it, all customers get the same database schema
> If you are happy to field the calls from sites where an update has
> failed, then I think you may be able to do something, but we like to
> test everything before passing it to a customer. Have all those
> 'specials' now become part of the later versions, or will they have to
> be new 'special' versions of the later code?
regardless of whether they have any special features or modifications
enabled, so it won't be a problem with the database. The only problem I can
see is keeping records of what version a customer has.
I got a call last week from a customer who bought our software 3 years ago,
its been working fine, but they someone crashed their server, and now they
need us to fix a corrupted database. No problem, but when I saw what
version they had, it was about 8 major versions behind the current shipping
product. This is an exception, but it does happen. Hence knowing how to
handle version upgrades from a situation like this during a software update
is critically important to us.
Thanks for the information on how you do it. We'll see what can be done for
Director of Engineering
Tech Solutions US, Inc.