You are right. No database introspection.
On Feb 21, 3:11 pm, Fred wrote:
> [Replying to old message; I'm way behind]
>
> On Jan 15, 1:21 am, pbreit wrote:
>
> > I think web2py compares the .table files to the
> > database to figure out what needs to be migrated.
>
> Is this correct? Everything
[Replying to old message; I'm way behind]
On Jan 15, 1:21 am, pbreit wrote:
> I think web2py compares the .table files to the
> database to figure out what needs to be migrated.
Is this correct? Everything I've seen suggests that web2py compares
the .table files to the model files (models/*.py)
Have you considered developing against rocket/sqlite?
CentOS should be fine. I've seen a lot of people happy with Ubuntu (10.04
or the latest). I've found Ubuntu to be easy to work with with lots of help
available.
Thanks, all. This is closed.
I am progressing to more deployment complexity:
locally develop on xampp with apache and mysql; occasionally run
rocket/sqlite if I can't figure things out
move things to SuSE server in my office and access behind firewall on
own network
move things to Linode (probabl
+1
On Jan 15, 1:21 am, pbreit wrote:
> Migrations are pretty powerful but problems can arise. As I've suggested
> elsewhere, best to develop against SQLite and then deploy as desired. In
> development, I change models frequently. If I run into a problem that I
> can't fix with migrations, I might
Migrations are pretty powerful but problems can arise. As I've suggested
elsewhere, best to develop against SQLite and then deploy as desired. In
development, I change models frequently. If I run into a problem that I
can't fix with migrations, I might delete the whole database folder and
start
The manual is pretty explicit about this although it simplifies a
bit. The manual says it looks at the existing tables (actually looks
at the physical file or looks at the most recent definition in
sql.log?). I think that the time stamps also matter. Not clear what
timestamp is being compared to
7 matches
Mail list logo
