Great! Good to hear it's mostly working now. I'm sure Chris and I will find
the problem with the user-creation tomorrrow morning.
Bye,
Erik.
On Fri, May 17, 2013 at 10:42 PM, Chris Calef wrote:
> And... DING DING DING!
>
> "This database operation has completed successfully. LedgerSMB may now
And... DING DING DING!
"This database operation has completed successfully. LedgerSMB may now be
used."
Thanks very much for all the help, that did it!
Just in case any other part time SQL newbies follow along here, the precise
syntax on create user for my version of postgres is:
create user cc
On Fri, May 17, 2013 at 9:41 PM, Chris Calef wrote:
> Hm,
>
> "This can be worked around easily enough by logging in with psql (as
> postgres, any db), and CREATE USER '[username]' before creating the
> database. Then you can select 'yes' in the import option and this works
> properly. However it
I went back and tried saying Yes to Import, not sure how that is supposed
to work, but with a new database name it fails because database doesn't
exist, and with a new user on an existing database I get the same "can't
grant permissions to a non existent user" message.
On Fri, May 17, 2013 at 1
Hm,
"This can be worked around easily enough by logging in with psql (as
postgres, any db), and CREATE USER '[username]' before creating the
database. Then you can select 'yes' in the import option and this works
properly. However it does need to be fixed before next beta."
Does [username] refer
On Fri, May 17, 2013 at 9:19 PM, Chris Calef wrote:
> Hmm... well, we got rid of all the errors in dblog!
>
> There was one more error after your commit, the same issue but with
> "journal__save_recurring_print" instead of "journal__save_recurring"... I
> went ahead and did the same RETURN * thin
Also, just so you know, I'm still getting a database created, but no users
added, at the point where it crashes (which is just after filling in the
new user information and clicking okay).
On Fri, May 17, 2013 at 12:19 PM, Chris Calef wrote:
> Hmm... well, we got rid of all the errors in dblog!
Hmm... well, we got rid of all the errors in dblog!
There was one more error after your commit, the same issue but with
"journal__save_recurring_print" instead of "journal__save_recurring"... I
went ahead and did the same RETURN * thing after that and the error went
away.
However, my browser stil
Hi Chris,
Nobody was working on it, so I took the liberty to commit a fix. Could you
tell me if it works now?
Bye,
Erik.
On Fri, May 17, 2013 at 8:31 PM, Chris Calef wrote:
> Hi, not sure if people are still in the middle of working on this, but I
> saw there were updates so I tried it again
Hi, not sure if people are still in the middle of working on this, but I
saw there were updates so I tried it again. Results: not _quite_ there,
but only one error this time!
The offending statement is this:
psql:sql/modules/Transaction_Templates.sql:161: ERROR: return type
mismatch in functio
I'm sorry I didn't notice this when it came out but shouldn't the
copyright year in locale/po/hu.po be "2013"? (If not something like
"2003, 2013"?)
--
Robert J. Clay
rjc...@gmail.com
--
AlienVault Unified Security Ma
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, et
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 wrote:
> Hi Chris,
>
> Still got quite a few er
13 matches
Mail list logo
