[IP-625] Bugfix some wrong columns and index #578
Conversation
…ames. Update code to acept composite primary keys and work with invoice custom. Alter some tables to new column name. Changed a primary key indice.
|
@denysvitali Could you check these changes for the custom fields? |
|
I've read the code, and it looks ok to me. I still have to test it though. I'll take a look at it this week |
…n is null to permite remove values
|
I've added other bugfix related, now enable to save custom field with empty value. |
|
@franciscorangel Could you outline what exactly the problem was and which errors occured while migrating from 1.4 to 1.5? Would like to know more about this as custom fields were working perfectly for me and did not encounter any errors. |
|
@franciscorangel Any news? |
Kovah
changed the title
|
I cannot reproduce the problem in v.5.9 and v1.5.10. Apparently this PR is no longer needed and may conflict with the code in v1.5.9/v1.5.10 (there is already a column named 'client_custom_fieldid') and/or in CI (changes to application/core/MY_Model.php). I recommend rejecting this PR as no longer needed for v1.5.10. |
Bugfix some parts of the code, changing all parts to the new column names, this problem started when I have done a update 1.4.x to 1.5.x
Update code to accept composite primary keys and work with invoice custom.
Alter some tables to new column name.
Changed a primary key index.