I would like you to implement a function to separate read/write endpoints as follows.
https://support.abp.io/QA/Questions/4870/I-want-to-Separate-DB-read-and-write-endpoints _
Thanks for your information. Btw, is the Timezone function configurable for each tenant? Or is it configurable per user?
Thanks, I understand that 7.4 expected to be released after August 15, 2023!
If possible, could you tell me in when 7.4 expected to be released?
thank you. I requested a consultant. Can I prevent this support ticket from being consumed?
thank you. Have you considered MySQL? If so, I would like to know why you excluded MySQL.
thank you. Any idea why Abp chose PostgreSQL?
I have already read the following articles. https://blog.abp.io/abp/Migrating-from-MS-SQL-to-Postgresql We understand that ABP chose PostgreSQL for its price advantage.
I found SQLServer to be very expensive. (I want you to answer intuitively.) Which do you think are the most popular ABP Commercial users, MySQL or PostgreSQL?
thank you.
Is it possible to write the DB endpoint in this URL? https://docs.abp.io/en/commercial/latest/modules/saas?&_ga=2.31513790.1017473141.1680852494-480170447.1680614778#connection-string
For example, for a company tenant, I want the host to be a.rds.cloud.
Server=a.rds.cloud;Database=a;Trusted_Connection=TrueTrustServerCertificate=True
Thank you very much.
However, it occurs in the future that we want to separate DB instances. As a use case, ・Enterprise companies ・When the number of companies reaches a certain number, we want to split the DB (e.g. 1 DB instance per year)
●Question If we customize ABP Commercial to achieve this, can we get consulting? Also, is the scope of influence of customization quite large?
●workaround Given the current constraints, I would take the following approach ・xxx-2023.portx.cloud → 2023 DB ・xxx-2024.portx.cloud → 2024 DB