a legacy db just needs migrate=False. Nothing else. Just as a production db
where migrations aren't needed in THAT single request.
tl;dr: The default for every NON "development-mylaptop-etc" environment
should be migrate=False. Let me reinstate once again: migrate=True is a
TOTAL WASTE of cpu when models aren't requiring any migration
back to you issue: if you're comfortable with executing queries by hand in
the database, a DAL line is all you need. If you want to leverage fancy
syntax over an Abstraction (where the A in DAL comes from), you kinda need
to define the Abstraction. Which, boiled down, means defining table models
you want to interact with.
On Tuesday, October 13, 2015 at 4:16:37 PM UTC+2, Gael Princivalle wrote:
>
> Hello all.
>
> In a web2py application I would like to insert/update user records in 2 db.
> The first one is the application db, a postgres db:
> db = DAL('postgres://user:pass@localhost:5432/my_web2py_app_db',
> check_reserved=['all'], pool_size=1, entity_quoting=True, bigint_id=True,
> migrate=True)
>
>
> The second one is used by a mailing program called php list. It's a mysql
> db.
> db_php_list = DAL('mysql://user:pass@localhost:3306/my_php_list_db',
> fake_migrate_all=False, migrate=True)
>
> I don't see any db_php_list table in database administration.
>
> Mysql port is 3306?
> For an existing db, I've to add 'fake_migrate_all=False, migrate=True',
> right?
>
> Admitting that I can connect to the mysql db, how can I handle the user
> insert/updates to both db?
>
> Thanks, regards.
>
>
>
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
