, it must be easy to automatize
this.
- It must be more simple to work with an existing DB and a new DB,
migrating data, synchronizing them, in a smooth way to replace the old
system, withouth stopping, aligning and testing both systems, still
everyone wants to use only the new system.
- It mu
ith causality. Except in that occasion I never had any problem with
> > sqlite and I do use it on production. On my web site (web2py.com) I
> > only run sqlite.
> >
> > Massimo
> >
> >
>
>
> >
>
--
Hernan Olivera
--~--~-~--~~---
gt; > run on different machines on a LAN and all access a single SQLite
>> > database on one of those machines. I am considering porting the
>> > applications to Web2py but I wonder if it will be possible to share
>> > the database in this
cimal point :)
--
Hernan Olivera
--
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to web...@googlegroups.com.
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com.
For mor
Is it really "enterprise"? Does it scale for full organization
systems? How huge are real web2py systems implemented?
I´m just starting a full org sys migration, now my bet is Django, but
I´m in time to let a try to web2py
What do you think?
thanks
--
Hern
5 matches
Mail list logo
