[mb-users] Digest of a personal thread that Fuchs started (Was: Uff ...)

[Ben]

UI testing is one thing, but you do *not* want to let a testing  
server modify your production data until you've validated that it  
won't corrupt stuff.

Not knowing anything about how the MB server interacts with the  
database, I'm not sure how realistic it would be to give a testing  
server a read-only account on the database.

On Aug 20, 2006, at 2:08 PM, Lukáš Lalinský wrote:

> Björn Krombholz wrote:
>> Allowing concurrent access of both servers (or 2 implementations of a
>> feature) on the same DB would need a new (or improved) layer between
>> the UI and the DB that allows mutex access to single entries in the
>> DB. And this wouldn't really work when it comes to DB schema changes.
>
> The DB already runs on its own server. And I really believe  
> PostgreSQL, like any
> other sane database server, can handle connections from multiple  
> clients without
> any problems. :)
>
> Of course this wouldn't work for testing versions with DB schema  
> changes, but
> those are not that often. And the primary purpose of this would be  
> UI testing,
> after all.
>
> -Lukáš
>
> _______________________________________________
> MusicBrainz-users mailing list
> MusicBrainz-users at lists.musicbrainz.org
> http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-users