Originally posted by partomas
View Post
For example, the software would only be able to do JOINS if the two databases are located on the same server and use the same connection (i.e. with the same database user credentials). This is a little-known feature of MySQL.
But, if the databases do not use the same connection, you can't use JOINS anymore when querying tables in different databases. While you could still get the data by using separate queries to each database, it makes it harder to sort results, since you can't use a JOIN. Maybe with some creativity, it can be done, but such a design forces you to rethink how you interact with the data.
Another possible solution would be to only store the meta information in the CRM database, and that points to the body of the email stored elsewhere, perhaps in another database or a file. The downside to this is you wind up using more disk space since you are storing the meta information twice, and it makes it difficult to search the body of the emails and cross reference that with other data in the CRM at the same time, again, because for the JOIN issue.
I'm not speaking for the developer, but I will note that it is technically possible but would probably require significant rewriting of the code.
Leave a comment: