MIT-LCP / querybuilder-issue

Public Issue tracker for the Query Builder repo
https://querybuilder-lcp.mit.edu
MIT License
2 stars 3 forks source link

Having trouble with Query Builder, particularly with CHARTEVENTS. Also having trouble building local database. #5

Open RJBeetel3 opened 7 years ago

RJBeetel3 commented 7 years ago

I'm not terribly experienced with POSTgreSQL or building databases so I'm trying to use the Query Builder to select and export data. I'm running into problems when I try to access CHARTEVENTS. The Builder hangs up and eventually returns a 501 error. I tried to download the mimic-code-master repository and use it to build a local database. I'm running into issues with POSTgreSQL password. The Makefile appears in OS X as an executable file that can't be opened using ext editors. I added a .txt extension which enabled me to edit the file and change my username from mimic to postgres. I removed the extension and tried to run the make command but got an error. Overall I'm not doing so well.

tompollard commented 7 years ago

I'm running into problems when I try to access CHARTEVENTS. The Builder hangs up and eventually returns a 501 error.

@RJBeetel3 sorry to hear that you've had some problems working with the data. What is the query that you are trying to run on querybuilder?

The Makefile appears in OS X as an executable file that can't be opened using ext editors. I added a .txt extension which enabled me to edit the file and change my username from mimic to postgres.

The Makefile is a plain text file that can be opened and edited in any text editor (changing the file extension does not affect the content).

I removed the extension and tried to run the make command but got an error.

If you post the error then we might be able to point you in the right direction. I would first suggest familiarising yourself with Postgres before you attempt to build MIMIC. There are some good tutorials online to get started.

tompollard commented 7 years ago

@RJBeetel3 By the way, for non-querybuilder-related questions (e.g. questions relating to the MIMIC build scripts and general MIMIC usage questions) we prefer issues to be raised on the MIMIC Code Repository: https://github.com/MIT-LCP/mimic-code Thanks!

RJBeetel3 commented 7 years ago

Hey Tom, Thanks for your prompt response. In the Query Builder, If I do something simple like: SELECT * FROM CHARTEVENTS it times out and gives the following error message.

Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error. More information about this error may be available in the server error log.

It will do this if I use a more specific query like SELECT subject_id, itemid FROM CHARTEVENTS

When I was downloading the compressed .csv files I was having trouble with one of them in that it wouldn't unzip. I believe it was the CHARTEVENTS file but I don't recall for sure.

I'll address the mimic build scripts questions to the mimic code repository. Thanks for the help!

elfeto commented 7 years ago

Hi Rob,

Thanks for reporting the bug, it should be fixed now. Since Querybuilder is for testing, the server automatically kills all queries that will runs for more than 15 minutes.

If you are new to PostgresQL, and you are exploring the data, I would suggest to add a limit to the query, i.e. SELECT * FROM CHARTEVENTS LIMIT 10000

RJBeetel3 commented 7 years ago

Hey effete, thanks for the help. I'll use the limit for experimenting but because I'm having serious difficulty building the PostgreSQL database locally I was hoping to use Query builder to get the data that I'd like to use compiled in a single table and export it. Do you think this is a possible use for the Query Builder tool?

elfeto commented 7 years ago

In short I would have to say no. We have to limit the output for the queries so that we can give service to more people. But it would also depend on the type of queries that you run to get the data.