[Vtigercrm-developers] Let's address the elephant in the room

[Sukhdev Mohan]

Hi All,

I thinks we all need to start addressing the elephant in the room. There are multiple things that can be improved and the most important one is the DB structure.
I see these problems/bottlenecks, please follow up with your impressions/thoughts and if you find other please add.

1. vtiger_modtracker_basic and vtiger_modtracker_detail: these table increase in size exponentially as the data grows, this slows down the db very much.
2. All the _seq tables: why can’t we just use auto_increment? It would be safer and there would be al most 50% less tables.
3. All the cf tables: why can’t we create the custom field in the main table with the name the dev choses instead of a cf_#### where #### is an arbitrary number with no meaning at all post creating.
4. Names for the standard tables: for instance if the module/entity in the crm is To Do you can’t store it in vtiger_activities. I propose to standardise naming scheme.
5. Implement True Object Relationship Mapping: frankly it would be a much more good thing If we could interrogate for entity and get the connected entities without doing n queries and cycle/traverse through and will lead to cleaner queries.
5.a Use of ORM such as Eloquent or Doctrine2 could be very good IMHO
6. Ditch AdoDB in favour of some more modern Library, even php’s native PDO is better, it might even have a low footprint.
7. Refactoring of the db structure in general will be a good step to improve the situation.


Best Regards,
Sukhdev Mohan | Software Developer







-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20201115/c27991fc/attachment.html>