Note, it is not necessary to bother with migrate=False if you are setting
migrate_enabled=False -- the latter will prevent all migrations (the former
is simply used to set the default value of the "migrate" argument for each
.define_table in case it is not explicitly set, but that is ignored whe
Then set the three variables Michele mentioned to false directly, it is not
necessary to create any metadata,
the following code snippet print the station name from a remote database
(vpn address), the powerful thing is that the table station has several
fields but I defined only once :)
db = DAL(
No,
I don't want to alter the 5 tables schema.
But I want to perform CRUD operations.
And it would be great if somehow I can restrict web2py from altering table
schemas all together as a J2EE application is running on the same the DB
and DB is a remote DB.
thanks,
Tushar Tuteja
On 9 January 2014
Mind that DAL should be instantiated with fake_migrate_all;
run your app once, then you can set it to false. This operation will create
several files (one for each defined table) in the app/databases/ directory
moreover, do you need to alter the 5 tables you mentioned?
Paolo
On Thursday, Janu
Instantiate the DAL with fake_migrate=True,
migrate=False,migrate_enable=False
Define the tables with only the fields you are going to need in a model
file.
This is going to create the metadata needed by web2py without touching your
legacy database schema.
2014/1/9 Tushar Tuteja
> I have a J2
I have a J2EE application and a database which has 200 tables in it.
I want to develop a new application using web2py, which would use only 5
tables.
I want to know how should I go about it. As I am not clear about how I
would use database without mapping all the 200 tables which is a huge task.
6 matches
Mail list logo
