Part of the work to make custom fields cross database compatible involved porting the findInSet
function to all database types. This was done for Mysql and Postgres in #12642 however MSSQL testing proved hard due to other MSSQL issues. This issue is a placeholder to test the MSSQL resolution before release of 3.7
Labels |
Added:
?
?
|
Milestone |
Added: |
findInSet
is not the best function in general for sql.
For now it is not used by any code. In Custom Fields
code has been changed in favour to use join syntax.
We may also consider to remove/revert it.
If that is the case go for removing it. I'd rather not cause us unnecessary problems
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-02-14 13:18:57 |
Closed_By | ⇒ | wilsonge |
Labels |
Removed:
?
|
Now that we have AppVeyor testing where do we stand on this?