Conflict with table name for picklist fields
If we add a custom picklist field using vtlib script, vtiger created a new table with name as vtiger_.
This causes conflicts a lot of time. Especially now with marketplace in place.
For example in a module we needed a field time_zone, but that field does not work as there already exists a table with name vtiger_time_zone.
Should be there a check, that if table exists, either do not create the field or append some sequence?
This has been happening since the earlier versions of vtiger. But with marketplace around and many extensions with various possibilities of field name, this is a critical issue.