Hi Guillaume,
In InsertRequest.parse, we test the parsing granularities and if we
have to consider columns, we try to find the column in the table. The
problem is that the columns list is not populated
Yes, column parsing is not supported on INSERT statements.
Is it me or is there an inconsistent behaviour? Or perhaps column and
column unique parsing granularities are not supported?
These are not supported anymore in 3.0.
ResultCache implementation with column and column_unique can impose a
significant parsing overhead without necessary substantial improvements.
If someone wants to look at this code, we can see if it's worth keeping
it or just dropping it altogether.
Let me know what you think,
Emmanuel
--
Emmanuel Cecchet
Chief Scientific Officer, Continuent
Blog: http://emanux.blogspot.com/
Open source: http://www.continuent.org
Corporate: http://www.continuent.com
Skype: emmanuel_cecchet
Cell: +33 687 342 685
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
