Additional DBs
Jamroom Developers
You would have to do something custom - there's nothing in Jamroom that allows it to work with 2 different databases at the same time. Sorry!
Forum Activity for @brian
Jamroom Developers
You would have to do something custom - there's nothing in Jamroom that allows it to work with 2 different databases at the same time. Sorry!
Additional DBs
Jamroom Developers
DannyA:Right. Isn't that my original question?
No - it's not
You're confusing "database" with "server". A single MySQL server can contain hundreds of databases. Moving your "data warehouse" to a different database on the same server is not going to lessen the load on the server. You need to create a second server and load your data warehouse data on the second server. This way the queries you run against your data warehouse do not impact the performance of your main server.
Additional DBs
Jamroom Developers
A "data warehouse" would be a completely separate server from your live server, that would allow you run ad hoc queries on the data without worrying about messing up your production data.
Additional DBs
Jamroom Developers
DannyA:I may have mis-communicated then. There are many microtransactions and very detailed reporting and analytics. So I want to separate that data so it doesn't slow down the main db when a report is generated. However, I still want to be able to query the new db using the Proxima APIs
Moving the data to a different DB won't do anything for performance - you need to either get a bigger server that can handle the load, or stream the data off to a replication slave. The reason is that in MySQL databases are just a logical abstraction - if your server is already suffering under load, splitting the data into multiple DB's will actually make a bit worse, since there is extra overhead for each DB that is "open".
Let me know if that helps.
Additional DBs
Jamroom Developers
DannyA:Don't you end up with the same data on both servers? The idea was to separate transactions data because it's a lot of microtransactions. It's causing a big load on main DB when we run reports
That's correct - based on what you posted I thought was what you were looking for?
Additional DBs
Jamroom Developers
You'd want to setup a MySQL replication slave server and run your queries from that slave server:
https://dev.mysql.com/doc/refman/5.7/en/replication-setup-slaves.html
Unable to put a link containing the string ".jpg" in a comment.
Using Jamroom
You should be good now - you had 3 templates that were using the incorrect value for the image URL:
index.tpl
item_list.tpl
profile_index_image.tpl
I've fixed those up and you should be good.
Unable to put a link containing the string ".jpg" in a comment.
Using Jamroom
Yeah I suspect the templates are using the wrong value for the URL - I'll check it out and let you know.
Unable to put a link containing the string ".jpg" in a comment.
Using Jamroom
What profile page is showing the image URL with the extension in place? Sounds like it could be a custom template that needs to be updated to use the correct URL.
Custom payment module.
Jamroom Developers
Just to echo what Michael has posted - the new payment module will come with 3 plugins:
FoxyCart
PayPal
Stripe
If you cannot use Stripe or Paypal, you will want to use FoxyCart since they support over 100 different gateways. However, you could also develop your own but it is far from trivial - every gateway has it's own unique setup and needs. You could sponsor the development of one through us if it is something you really need but it's not supported in FoxyCart.
