On Fri, May 25, 2012 at 12:01 PM, Sebastian Weitmann <[email protected]> wrote: > On Wed, 2012-05-23 at 15:04 +0500, Armaghan Saqib wrote: >> Hi Sebastian, >> >> Please run sql/Pg-custom_tables.sql on each dataset *before* running >> sql-ledger (this was probably not clear from my email). >> >> To run it from command line: >> cd /usr/local/sql-ledger/ >> psql -U username dbname < sql/Pg-custom_tables.sql > > Good morning Armaghan, > > I have been doing some more testing and found that, in order NOT to get > the error message > > ------------------ > DBD::Pg::db selectrow_array failed: ERROR: column e.department_id does > not exist > LINE 4: LEFT JOIN department d ON (d.id = e.department_id) > ^ at SL/User.pm line 633. > ------------------ > > when I login for the first time on your enhanced Version 3.0.2, after > having upgraded from your enhanced Version 2.8.33, I need to do the > following: > > a.) Login one time and see the message "Upgrading to Version 3.0.2 ...", > but then NOT click on 'Continue'; > > b.) then run sql/Pg-custom_tables.sql according to your instructions > above; > > c.) and finally login a second time. > > If I run sql/Pg-custom_tables.sql *before* logging in the first time and > then click on 'Continue' when I login after that, I always still get the > error message above. > > It seems to be necessary to do the three steps in the order I have > stated them here above to avoid the error message. Do you agree? Or am I > still doing something wrong here?
Hi Sebastian, Good morning, You are right. In short you just need to run sql/Pg-custom_tables on your databases *before* logging into new sql-ledger version. Regards Armaghan _______________________________________________ SQL-Ledger mailing list [email protected] http://lists.ledger123.com/mailman/listinfo/sql-ledger
