OK
pydal.py/base.py:
TABLE_ARGS=set((... , 'insert_with_returning'))
pydal.py/objects.py:
class Table(object):
...
def __init__(...):
...
self._insert_with_returning=args.get('insert_with_returning', True)
...
pydal.py/adapters/postgres.py:
def
Can you tell us about the fix?
On Friday, 13 March 2015 16:30:39 UTC-5, Val K wrote:
Thanks for your reply!
You are right, if we are talking about some application with full built-in
logic and it would like to be independent on any DBEngine. But IMHO there
are a lot of opposite situations:
Thanks for your reply!
You are right, if we are talking about some application with full built-in
logic and it would like to be independent on any DBEngine. But IMHO there
are a lot of opposite situations: DB-App with many different clients. In
this case VIEW is very helpful solution, it
IMHO inserting to a view shouldn't be supported at all.
On Thursday, March 12, 2015 at 12:18:10 AM UTC+1, Val K wrote:
OK guys!
My concrete suggestion:
- Add attrubute _insert_with_returning to Table class
- Fix adapter Postgres.py :
def _insert(self, table, fields):
OK guys!
My concrete suggestion:
- Add attrubute _insert_with_returning to Table class
- Fix adapter Postgres.py :
def _insert(self, table, fields):
table_rname = table.sqlsafe
if fields:
keys = ','.join(f.sqlsafe_name for f, v in fields)
5 matches
Mail list logo
