Just letting folks know:
With svn 5815 I was able to create a new fresh db. It took a bit longer
because the new Roles.sql format doesn't get processed as quickly as the
old format (however, it is now transactional and does a bunch of sanity
checks which make it better for working with addons, etc).
I still ran into one significant setup bug but it has a fairly simple
workaround. I expect to get it fixed soon. The bug report is at
https://sourceforge.net/p/ledger-smb/bugs/826/ for anyone who wants to
follow, and the workaround is listed there.
Best Wishes,.
Chris Travers
On Fri, May 17, 2013 at 3:52 AM, Chris Travers <[email protected]>wrote:
> Just letting everyone know, I am working on the Roles.sql, entirely
> rewriting it so that it runs repeatably and transactionally.
>
> I expect to have it committed shortly.
>
> Best Wishes,
> Chris Travers
>
>
>
>
> On Thu, May 16, 2013 at 11:46 PM, Erik Huelsmann <[email protected]> wrote:
>
>> Hi Chris,
>>
>> Still got quite a few errors, although you fixed several with that
>>> round...
>>>
>>> There was one more report_id vs adjust_id problem in
>>> Inventory_Report.sql, line 53, fixed that myself but you'll want to do it
>>> in the repo:
>>>
>>> psql:sql/modules/Inventory_Report.sql:58: ERROR: column l.report_id
>>> does not exist
>>>
>>> LINE 8: JOIN inventory_report_line l ON l.report_id = r.id
>>>
>>>
>> Fixed this one and found another one (just by inspecting the code).
>>
>>
>>>
>>> Then, Transaction_Templates.sql had this now:
>>>
>>> psql:sql/modules/Transaction_Templates.sql:134: ERROR: missing "LOOP"
>>> at end of SQL expression
>>> LINE 22: j.transaction_date);
>>>
>>>
>> Found a spurious semicolon. Removed. That should fix it.
>>
>>
>>>
>>> Goods.sql is fixed now.
>>>
>>> Still having trouble with some more of those menu_node ids. I'll just
>>> summarize them here with the bad node id, they are all in my lsmb_roles.sql:
>>>
>>> DETAIL: Key (node_id)=(28) is not present in table "menu_node".
>>> DETAIL: Key (node_id)=(29) is not present in table "menu_node".
>>> DETAIL: Key (node_id)=(17) is not present in table "menu_node".
>>> DETAIL: Key (node_id)=(18) is not present in table "menu_node".
>>> DETAIL: Key (node_id)=(87) is not present in table "menu_node".
>>> DETAIL: Key (node_id)=(88) is not present in table "menu_node".
>>> DETAIL: Key (node_id)=(89) is not present in table "menu_node".
>>> DETAIL: Key (node_id)=(90) is not present in table "menu_node".
>>> DETAIL: Key (node_id)=(93) is not present in table "menu_node".
>>> DETAIL: Key (node_id)=(94) is not present in table "menu_node".
>>> DETAIL: Key (node_id)=(220) is not present in table "menu_node".
>>> DETAIL: Key (node_id)=(221) is not present in table "menu_node".
>>>
>>>
>> I'll do these in the course of the day: I want to be sure to remove the
>> right bits in that table.
>>
>> Bye,
>>
>> Erik.
>>
>>
>> ------------------------------------------------------------------------------
>> AlienVault Unified Security Management (USM) platform delivers complete
>> security visibility with the essential security capabilities. Easily and
>> efficiently configure, manage, and operate all of your security controls
>> from a single console and one unified framework. Download a free trial.
>> http://p.sf.net/sfu/alienvault_d2d
>> _______________________________________________
>> Ledger-smb-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
>>
>>
>
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Ledger-smb-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
