Saptarshi --
There seems to be a body of people who believe that Postgres
performs better than MySQL.
Also, many companies and government agencies (and even donors!)
have policies about which database server to use. There are perceived
advantages to them in terms of deployment strategy, software maintenance,
personnel training, standard operating procedures, etc.
I think the problems we are facing are a result of not looking
at the liquibase scripts with a more critical eye. The most useful
non-standard features of MySQL are commands like CREATE IF NOT EXISTS, INSERT
ON DUPLICATE KEY UPDATE, UPDATE IGNORE. Some of these commands can be emulated
by multi-step processes using standard SQL. In some cases, preconditions can
be checked by liquibase, but it may be that liquibase lacks certain
functionality relating to exception handling. While liquibase has bought us a
lot over sql-diffing, it could be we need more.
As for data types, perhaps there is a way to have liquibase
work at the Hibernate level. (Now that is a policy that needs questioning, do
we really need to allow for other ORFs?) In a similar vein, I was looking at
the Jasper Reports module the other day. It was set up to use only the MySQL
driver; until recently, OpenMRS core was set up to recognize only 6 or so
drivers (there's now an optional driver entry in the properties file). But
Jasper Reports can work with a Hibernate connection and HQL, doing so could
have gotten multi-DB capability at no cost (except learning HQL), I guess that
wasn't thought of/pursued. Perhaps liquibase could/should work at that level
as well (which would probably synchronize the hbm.xml updates with the DB
changes for free).
So please don't take your frustrations with Tomcat out on
blameless Postgressors.
From: [email protected] [mailto:[email protected]] On Behalf Of Saptarshi
Purkayastha
Sent: Wednesday, August 10, 2011 8:20 AM
To: [email protected]
Subject: Re: [OPENMRS-DEV] Supporting 2 Million Patients
I was looking through this discussion and wanted to know how much of a priority
is it for the community to run OpenMRS on Postgres or MSSQL?? Other than
once-in-a-while mails on the dev list?? Is it our core motivation to have users
choose what database they want OpenMRS to work on??
It is some amount of work (upgrading liquibase is definitely required, adding
database drivers and changing mysql-specific - tinyint to smallint, longtext
etc.).
Also among other things, I've yesterday had problems with simultaneous users
(75+) using the system (16GB+ server) and getting out of memory and having to
restart the system every 12-14hrs to release memory. The memory usage goes on
increasing for Tomcat and restarting the server seems like the simple solution
for the time being. I've heard Paul talk about a similar problem at AMPATH in
one of the conf call recordings. Has there been a workaround at AMPATH or is
restarting Tomcat the accepted solution?? I'm planning to host OpenMRS on
Glassfish (with its better monitoring tools and VisualVM integration) and also
write a performance monitoring module that uses
javamelody<http://code.google.com/p/javamelody/>, but any suggestions in the
meantime should be useful...
---
Regards,
Saptarshi PURKAYASTHA
My Tech Blog: http://sunnytalkstech.blogspot.com
You Live by CHOICE, Not by CHANCE
On 27 July 2011 18:18, Ben Wolfe <[email protected]<mailto:[email protected]>>
wrote:
I think this was the ticket I was thinking of:
https://tickets.openmrs.org/browse/TRUNK-1925
That ticket should be edited to be more general about supporting all databases.
The removal of the "not exists" from the wizard is just one part of that.
The openmrs app does run on everything. And I'm pretty sure the update wizard
/ liquibase changesets run on everything. So a quick fix would be to install
to mysql, then export the database tables and import those into postgresql.
Ben
On Wed, Jul 27, 2011 at 1:44 PM, Suranga Kasthurirathne
<[email protected]<mailto:[email protected]>> wrote:
Hi,
Looks like you could do with an Openmrs Id,
go to https://wiki.openmrs.org/display/RES/OpenMRS+ID, and create your id, this
will let you interact (and yes, create tickets) easily.
once you create an id, you can use it to log in, and use JIRA.
after signing in, go to https://tickets.openmrs.org/secure/Dashboard.jspa and
click on 'create issue' (on the top right of screen).
Hope this helps.
On Wed, Jul 27, 2011 at 4:04 PM, Sokha RUM
<[email protected]<mailto:[email protected]>> wrote:
I look for the existing ticket, and i found a ticket TRUNK-1922 which is
about the supporting 6 types of database including also PostgreSQL. But that
ticket is already in status "Fixed".
One more thing i wanted to create a new ticket, but could not login. I do
not know if i can use the account for joining community to access to ticket
of OpenMRS.
_________________________________________
To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to
[email protected]<mailto:[email protected]> with "SIGNOFF
openmrs-devel-l" in the body (not the subject) of your e-mail.
[mailto:[email protected]<mailto:[email protected]>?body=SIGNOFF%20openmrs-devel-l]
--
Best Regards,
Suranga
________________________________
Click here to
unsubscribe<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l>
from OpenMRS Developers' mailing list
________________________________
Click here to
unsubscribe<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l>
from OpenMRS Developers' mailing list
