[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Redevelope backend database access

From: Andy Levy <andy.levy_at_gmail.com>
Date: Tue, 14 Apr 2009 06:33:20 -0400

On Mon, Apr 13, 2009 at 23:28, Alan Tse <alan.tse_at_trafficnet.com.au> wrote:
> We are re-developing our application using different backend database from .dbf to MySQL. Also we need to change the way how to access the MySQL using different database access components in application.
> What do you think we should do with the subversion? Do a branching or something else? Or even start a new project in subversion?

If your application is designed properly, only those areas of it which
deal with the direct database access should be impacted (this is also
a not-so-subtle hint to build in a DB abstraction layer if needed on
the new version, so you aren't doing this again when you switch to
PostgreSQL or MSSQLServer or Oracle).

Would starting a new project (which is a word you'd have to define
here - a complete fork within the same repository, or a new repository
altogether) provide any benefit that outweighs the drawback of (if you
create a new repository) dropping all history?

I'd branch, and merge in changes from the "old" version on a regular
basis since you'll presumably be doing maintenance on the old code
instead of stopping everything while the rewrite is happening..


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-04-14 12:33:34 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.