esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Pollak <>
Subject Re: Breaking changes to the schema
Date Sun, 02 Aug 2009 21:00:22 GMT
My plan was to completely revise the User table to allow for multiple
authenication types as well as supporting message signing (the precursor
step to federation)

It will be difficult to preserve the tables (including the Users and the
Messages) unless I plan to do so from the beginning.  The cost is about 30%
more work.

On Sun, Aug 2, 2009 at 12:50 PM, Vassil Dichev <> wrote:

> > If I made breaking changes to the schema that ESME uses, how many of you
> > will need a migration script from old to new?
> Merging the pools branch involved breaking DB changes as well and
> AFAIK there were no complaints to Dick when he asked about nuking the
> DB.
> The most valuable information to keep is messages, and they are
> volatile info anyway- they're gone from the timeline when there are 40
> newer messages. I suspect that nobody will mind, especially if the
> tradeoff is a particularly compelling new feature... which we are now
> only guessing :)
> Vassil

Lift, the simply functional web framework
Beginning Scala
Follow me:
Git some:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message