sunsetsystems wrote on Tuesday, April 19, 2005:
I have just updated the INSTALL file a bit and changed the version number in globals.php to "2.7.2-rc1" (as in Release Candidate 1).
Who can install and test the current code and identify last-minute bugs to fix? Also, who is planning to do other fixes for the release, like installing the new logo?
– Rod <rod at susnetsystems dot com>
emilykillian wrote on Tuesday, April 19, 2005:
I can e-mail the logo to whoever volunteers for that, if needed.
andres_paglayan wrote on Tuesday, April 19, 2005:
already replaced
andres_paglayan wrote on Tuesday, April 19, 2005:
I just run an installation and went fine.
also just got a whole new set of documentation sent by Emily that I am about to commit.
sunsetsystems wrote on Tuesday, April 19, 2005:
Andres, that’s great.
Are we including FreeB in the release?
I have some hopes that the current SQL-Ledger from sql-ledger.org will work if we just throw in ws_server.pl, so perhaps we should not include SL. If would be cool if someone could try that. Unfortunately I’m bogged down with tasks for clients right now and so cannot do it myself.
– Rod <rod at sunsetsystems dot com>
tekknogenius wrote on Wednesday, April 20, 2005:
Are you saying that the current (soon to be 2.7.2) no longer makes changes to sql-ledger (besides ws_server.pl)? That would be great! I’ll test it out later on today.
sunsetsystems wrote on Wednesday, April 20, 2005:
I’m saying that I can’t think of any reason why it should not work if you take a stock SQL-Ledger and add in ws_server.pl (and the US Medical chart of accounts) from OpenEMR. But I’ve been wrong before…
Be sure to check the new options in interface/globals.php related to SQL-Ledger.
– Rod <rod at sunsetsystems dot com>
tekknogenius wrote on Thursday, April 21, 2005:
It seems that the US_Medical-chart.sql has issues when sql-ledger tries to update it. It seems that a colum already exists and then it locks the database down. I tried it using the default chart of accounts from the sql-ledger 2.4.11. I’ll look at the differences between the two to see what I can find.
tekknogenius wrote on Thursday, April 21, 2005:
Changed the version in US_Medical-chart.sql to 2.4.4 from 2.4.3 then created the dataset. If dataset is already created, then use psql to change it:
update defaults set version=‘2.4.4’;
sunsetsystems wrote on Thursday, April 21, 2005:
Yeah try a normal chart of accounts. I didn’t realize US Medical had all that weird stuff in there.
– Rod <rod at sunsetsystems dot com>
tekknogenius wrote on Thursday, April 21, 2005:
$sl_dbname = ‘’; //sql-ledger database name
$sl_dbuser = ‘’; //sql-ledger database login name
$sl_dbpass =’’;//sql-ledger database login password
in globals.php
What should these values be? I’m assuming that the sql-ledger database login name is not the same as the values in config.php
$GLOBALS[‘oer_config’][‘ws_accounting’][‘username’] = “”;
$GLOBALS[‘oer_config’][‘ws_accounting’][‘password’] = “”;
sunsetsystems wrote on Thursday, April 21, 2005:
$sl_dbname is the name of the sql-ledger database, perhaps "sql-ledger"? $sl_dbuser and $sl_dbpass are to authenticate the postgres connection to the database; you also put these in the user info when you were setting up SL users with admin.pl.
The $GLOBALS username and password are for the SQL-Ledger user that ws_server.pl will pretend to be when it is doing its thing.
– Rod <rod at sunsetsystems dot com>
tekknogenius wrote on Thursday, April 21, 2005:
I thought so. I’m just getting an access error I can’t figure out at the moment:
I’m getting the “can’t connect to datasource, no database driver specified …” error when it trying to get the patient’s balance. I’m sure I have the names and passwords set up correctly.
Something is incorrect for sure though… still searching
ajperezcrespo wrote on Thursday, April 21, 2005:
Ok I also changed the US_Medical-chart.sql to 2.4.4 and ended up with this when creating the dataset:
CREATE SEQUENCE eob_id INCREMENT BY 1 NO MAXVALUE NO MINVALUE CACHE 1 ERROR: parser: parse error at or near "BY" at character 38
By the way I used the setup.pl to install SQL-Ledger off the site then I CHOWNed it to apache.
sunsetsystems wrote on Thursday, April 21, 2005:
The database driver is "Pg" for PostgreSQL. You should see this as an option when you are administering the user info, and you must select it.
– Rod <rod at sunsetsystems dot com>
tekknogenius wrote on Thursday, April 21, 2005:
Sorry, I didn’t get such an error.
sunsetsystems wrote on Thursday, April 21, 2005:
Try re-creating the database without using the US Medical COA. We want to get this working with a "normal" sql-ledger install, right?
– Rod <rod at sunsetsystems cot com>
tekknogenius wrote on Thursday, April 21, 2005:
It is selected. I think the problem is that $oemr_username, where is this supposed to be set? Perhaps in the sql-ledger.conf. I think that is where it was set before, but I didn’t set it this time (using the 2.4.11 version) I only used the default sql-ledger.conf file. I’ll add it there and see if that fixes things.
tekknogenius wrote on Thursday, April 21, 2005:
Yes, we do want it work under non-altered sql-ledger. Still, will need to change either sql-ledger.conf or ws_server.pl for the oemr_username variable (or any other oemr_ variable required). If nothing else in sql-ledger uses these variables other than ws_server.pl, then the variables should go there instead of sql-ledger.conf.
Is this correct?
sunsetsystems wrote on Thursday, April 21, 2005:
Check sql-ledger.conf from the openemr sql-ledger repository. There are several other things in there that you need also. Also note the "use vars qw" statement at the top.
– Rod