On 4/14/06, Jens Vagelpohl <[EMAIL PROTECTED]> wrote:
> > My thought was then that I could point both the production server and
> > the test server at that DB server.
> There is no problem setting that up, but it is plain *bad bad
> practice*! Do not do this unless you want to risk corrupting
> production data by experimenting and developing on the development
I think I wasn't being clear, the idea would of course be to mirror
the production database for development and testing and only point to
the live DB when the build was approved. The problem I'm having right
now is that the developer who's working on the project, when I can
convince him to work off line, will pull a snapshot of the instance
and develop on it, then pushing it back up when done with the coding.
Of course this steps on any new data that has been added to the ZoDB
since he took his snapshot.
And before you ask, no I can't replace him or command him (volunteer
project). All I can do is push really hard to create an environment
that makes it easy for him to do the right thing, which is what I'm
attempting to do.
> > It was my understanding though that you can use an external DB in
> > conjunction with the ZoDB, wouldn't it be possible to put my
> > client-entered data (form responses mostly) on this external DB ?
Can you give me an idea of the level of effort to accomplish this
partial data abstraction ? I imagine it's not so straight forward
since he has pushed back pretty hard to my initial requests but I
figured it's worth asking about as he may simply not know how to go
Zope-DB mailing list