PostgreSQL instead of MySQL
Posted: Thu Mar 04, 2010 10:10 pm
I read in one post (http://forum.opencart.com/viewtopic.php ... t=45#p3907) that it is possible to choose PostgreSQL for the database engine. However, since I am not able to find any other hits, I suspect that it is only a potential future capability.
I ask because I am configuring a small store that will have pretty low volume, but also needs to be low-maintenance, and be able to automatically manage customer_groups (used as membership levels) based on purchases of said memberships.
I have much more experience with PostgreSQL, than either PHP or MySQL. However, it wasn't too difficult to implement the necessary logic with MySQL's SQL/PSM. An INSERT in order_history would TRIGGER an UPDATE in the customer.customer_group_id where the order status was complete and the SKU matched a specific pattern.
This worked reliably when I tested it on my local virtual server, but when I tired to migrate it to the production server I discovered that the bargain hosting company has triggers disabled even though they do have MySQL 5.
Since, it turns out that the ISP's PostgreSQL server does not have the same limitations imposed, I thought I
could simply migrate over to PostgreSQL. Is sticking with the same ISP and pursuing PostgreSQL as the database engine promising, or should I really just upgrade the hosting plan, possibly to another ISP?
Thank you in advance if someone can point me in the right direction!
Thanks,
Randall
I ask because I am configuring a small store that will have pretty low volume, but also needs to be low-maintenance, and be able to automatically manage customer_groups (used as membership levels) based on purchases of said memberships.
I have much more experience with PostgreSQL, than either PHP or MySQL. However, it wasn't too difficult to implement the necessary logic with MySQL's SQL/PSM. An INSERT in order_history would TRIGGER an UPDATE in the customer.customer_group_id where the order status was complete and the SKU matched a specific pattern.
This worked reliably when I tested it on my local virtual server, but when I tired to migrate it to the production server I discovered that the bargain hosting company has triggers disabled even though they do have MySQL 5.
Since, it turns out that the ISP's PostgreSQL server does not have the same limitations imposed, I thought I
could simply migrate over to PostgreSQL. Is sticking with the same ISP and pursuing PostgreSQL as the database engine promising, or should I really just upgrade the hosting plan, possibly to another ISP?
Thank you in advance if someone can point me in the right direction!
Thanks,
Randall