Diptanu, to answer your question from earlier. we didn't intentionally put mysql-specific things in the liquibase file. Rather people used things like the "text" datatype without realizing they're mysql-specific, and nobody has simultaneously had the cycles and the interest in cleaning it up.
(Also, although liquibase supports some helper datatypes, IIRC none of them produce text or mediumtext in mysql, and those types are incredibly convenient.) -Darius On Wed, Aug 10, 2011 at 4:08 PM, Friedman, Roger (CDC/CGH/DGHA) (CTR) < [email protected]> wrote: > Saptarshi --**** > > I don't think we have an obligation to support more than > one DB out of the box. We can require users of other DBs to copy the jdbc > driver into some neutral spot (say Tomcat/lib, which I think is what DHIS2 > uses), or as Diptanu said point OpenMRS to it, or have a runtime property > pointing to it (like liquibase). We certainly don't want to be in the > position of automatically upgrading the driver to the latest version when > the user might be wanting to keep in synch with some other piece of software > or have a licensing or compatibility issue.**** > > Incidentally, liquibase does support HQL and furthermore > has a Hibernate integration that diffs the hbm.xml to the database.**** > > ** ** > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Saptarshi > Purkayastha > *Sent:* Wednesday, August 10, 2011 1:16 PM > > *To:* [email protected] > *Subject:* Re: [OPENMRS-DEV] Supporting 2 Million Patients**** > > ** ** > > From what I've tried we will have to add: postgresql-9.0-801.jdbc4.jar to > the WEB-INF/lib for postgres**** > > For other drivers similar connectors have to be added to the libraries.*** > * > > ** ** > > For the datatypes, liquibase 2.0.0 has automatic conversions > <http://forum.liquibase.org/topic/postgres-with-type-longtext-and-best-practice-for-supporting-multiple-database>for > common types between databases. **** > > There are also extensions that can be written for our mods.**** > > ** ** > > --- > Regards, > Saptarshi PURKAYASTHA > > My Tech Blog: http://sunnytalkstech.blogspot.com > You Live by CHOICE, Not by CHANCE > > **** > > On 10 August 2011 22:31, Friedman, Roger (CDC/CGH/DGHA) (CTR) < > [email protected]> wrote:**** > > Seems like there shouldn't be a dependency at all, the code should just try > to instantiate the appropriate driver. See > openmrs-api/src/main/java/org/openmrs/util/DatabaseUtil.loadDatabaseDriver. > This code is a TODO for > openmrs-web/src/main/java/org/openmrs/web/filter/initialization/InitializationFilter.executeStatement. > **** > > **** > > The MySQL driver is hard coded in > openrs-webapp/src/main/webapp/META-INF/context.xml, and in > openmrs/liquibase.build.xml. Seems like context could be set dynamically > when the loadDatabaseDriver code is executed. Maybe liquibase could be > edited at that time as well.**** > > **** > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Saptarshi > Purkayastha > *Sent:* Wednesday, August 10, 2011 12:03 PM**** > > > *To:* [email protected] > *Subject:* Re: [OPENMRS-DEV] Supporting 2 Million Patients**** > > **** > > Hi Roger,**** > > **** > > On 10 August 2011 19:18, Friedman, Roger (CDC/CGH/DGHA) (CTR) < > [email protected]> wrote:**** > > So please don't take your frustrations with Tomcat out on > blameless Postgressors.**** > > **** > > Definitely not frustrated about Tomcat or MySQL/Postgres. Wanted to see if > we are fine to add those drivers, which are currently not in the > dependencies. There are also issues which we will have to support and people > will have different problems associated with those databases. If developers > use MySQL and will not be able to solve issues with other databases, do we > want to take that route?? I understand the reasons you mention and I'm very > much supportive to the idea of using multiple databases and giving users > that choice.**** > > **** > > With the issues I listed in the last email, I'm also of the opinion > postgres has features that I would like to use and hence work on that > ticket. But before I went out and fixed those, I wanted to understand if the > patch will be accepted and we want to go ahead with the required changes.* > *** > > **** > > --- > Regards, > Saptarshi PURKAYASTHA > > My Tech Blog: http://sunnytalkstech.blogspot.com > You Live by CHOICE, Not by CHANCE**** > > **** > > **** > > *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]> 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]> 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]> 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] with "SIGNOFF openmrs-devel-l" in the body > (not the subject) of your e-mail. > > [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]**** > > > > **** > > -- > Best Regards,**** > > **** > > Suranga**** > > **** > ------------------------------ > > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > **** > > **** > > **** > ------------------------------ > > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > **** > > **** > ------------------------------ > > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > **** > > ** ** > ------------------------------ > > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > **** > _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
