Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

spatial loading via GUI is broken #230

Open
bjhecht opened this issue Mar 8, 2015 · 4 comments
Open

spatial loading via GUI is broken #230

bjhecht opened this issue Mar 8, 2015 · 4 comments
Labels

Comments

@bjhecht
Copy link
Collaborator

bjhecht commented Mar 8, 2015

hardcoded username, some bug with password, dbname not correctly written to customized.conf, etc.

@bjhecht bjhecht added the bug label Mar 8, 2015
@shilad
Copy link
Owner

shilad commented Mar 8, 2015

I've tested, but not in the last few releases.

That stuff should all be written correctly as long as you've selected
Postgres as your main database. Could you attach the relevant
customized.conf?

On Sun, Mar 8, 2015 at 1:07 PM, Brent Hecht [email protected]
wrote:

hardcoded username, some bug with password, dbname not correctly written
to customized.conf, etc.


Reply to this email directly or view it on GitHub
#230.

@bjhecht
Copy link
Collaborator Author

bjhecht commented Mar 8, 2015

Screenshot and conf file attached :) Thanks! Getting back into the swing of things here :)

screen shot 2015-03-08 at 1 39 43 pm

--- conf file ---
baseDir : "/wikibrain"

dao.dataSource.default : psql

dao.dataSource.h2.url : "jdbc:h2:"${baseDir}"/db/h2;LOG=0;CACHE_SIZE=65536;LOCK_MODE=0;UNDO_LOG=0;MAX_OPERATION_MEMORY=100000000"

dao.dataSource.psql.url : "jdbc:postgresql://localhost/wikibrain_spatial"
dao.dataSource.psql.username : "bjhecht"
dao.dataSource.psql.password : "[C@35d8cf6d"

dao.dataSource.postgis.host : "localhost"
dao.dataSource.postgis.port : "5432"
dao.dataSource.postgis.database : "wikibrain_spatial"
dao.dataSource.postgis.user : "bjhecht"
dao.dataSource.postgis.passwd : "[C@4d3bbe9c"

@bjhecht
Copy link
Collaborator Author

bjhecht commented Mar 8, 2015

Also, this occurs with 'h2' as the database as well. Perhaps we should force Postgres if they choose spatial?

@shilad
Copy link
Owner

shilad commented Mar 8, 2015

Good idea. Could you create a separate bug for that, and rename this one to
be more specifically about PG? What happens if you add a fake password?
Everything looks good in the configuration except for the password field.

On Sun, Mar 8, 2015 at 1:42 PM, Brent Hecht [email protected]
wrote:

Also, this occurs with 'h2' as the database as well. Perhaps we should
force Postgres if they choose spatial?


Reply to this email directly or view it on GitHub
#230 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants