Re: [GENERAL] Problems Importing table to pgadmin

2016-12-07 Thread Metare Solve
Melvin: haha, yeah, it's a download from the Clark County, NV voterfile website. It's just the format they send out to people who request the file. I worked this summer doing QA on voterfile builds so I'm familiar with the data. I thought it would be good stuff to start with. But thank you for

Re: [GENERAL] Problems Importing table to pgadmin

2016-12-07 Thread Melvin Davidson
On Wed, Dec 7, 2016 at 8:25 PM, Adrian Klaver wrote: > On 12/07/2016 05:19 PM, metaresolve wrote: > >> Uh, yeah, it was a SELECT * from cc_20161207; >> >> I know, it was dumb. I didn't realize it would break it or at least run >> for >> a while. I tend to do things in

Re: [GENERAL] Problems Importing table to pgadmin

2016-12-07 Thread Adrian Klaver
On 12/07/2016 05:19 PM, metaresolve wrote: Uh, yeah, it was a SELECT * from cc_20161207; I know, it was dumb. I didn't realize it would break it or at least run for a while. I tend to do things in small steps, run a query, check my results, then tweak. You're right, I wouldn't want to be

Re: [GENERAL] Problems Importing table to pgadmin

2016-12-07 Thread metaresolve
Uh, yeah, it was a SELECT * from cc_20161207; I know, it was dumb. I didn't realize it would break it or at least run for a while. I tend to do things in small steps, run a query, check my results, then tweak. You're right, I wouldn't want to be viewing those million. so I guess I could just be

Re: [GENERAL] Problems Importing table to pgadmin

2016-12-07 Thread John R Pierce
On 12/7/2016 4:02 PM, metaresolve wrote: I used to use Access to do my data crunching, matching, and cleaning at my old job. I worked with a max of 600k records so Access could handle it. I know, lame, but it's what I knew. Access is really 2 completely different things bundled. One is that

Re: [GENERAL] Problems Importing table to pgadmin

2016-12-07 Thread Adrian Klaver
On 12/07/2016 04:54 PM, metaresolve wrote: Choking: I get the "Waiting for the query execution to complete" circling around for a while. I tried shutting it down and trying again but it's still freezing on the execution. But if the TB are accurate, I wonder why it's slowing on this? Any

Re: [GENERAL] Problems Importing table to pgadmin

2016-12-07 Thread John R Pierce
On 12/7/2016 4:54 PM, metaresolve wrote: Choking: I get the "Waiting for the query execution to complete" circling around for a while. I tried shutting it down and trying again but it's still freezing on the execution. But if the TB are accurate, I wonder why it's slowing on this? Any thoughts?

Re: [GENERAL] Problems Importing table to pgadmin

2016-12-07 Thread Adrian Klaver
On 12/07/2016 04:54 PM, metaresolve wrote: Choking: I get the "Waiting for the query execution to complete" circling around for a while. I tried shutting it down and trying again but it's still freezing on the execution. But if the TB are accurate, I wonder why it's slowing on this? Any

Re: [GENERAL] Problems Importing table to pgadmin

2016-12-07 Thread metaresolve
Choking: I get the "Waiting for the query execution to complete" circling around for a while. I tried shutting it down and trying again but it's still freezing on the execution. But if the TB are accurate, I wonder why it's slowing on this? Any thoughts? -- View this message in context:

Re: [GENERAL] Problems Importing table to pgadmin

2016-12-07 Thread Tom Lane
Adrian Klaver writes: > On 12/07/2016 04:02 PM, metaresolve wrote: >> How many records and relational tables can pgadmin/postgres actually handle? > https://www.postgresql.org/about/ > So you have plenty of head room. Well, pgadmin and postgres are two different

Re: [GENERAL] Problems Importing table to pgadmin

2016-12-07 Thread Adrian Klaver
On 12/07/2016 04:02 PM, metaresolve wrote: That's a little beyond me. Let me back up a sec and maybe you guys can help. I used to use Access to do my data crunching, matching, and cleaning at my old job. I worked with a max of 600k records so Access could handle it. I know, lame, but it's

Re: [GENERAL] Problems Importing table to pgadmin

2016-12-07 Thread metaresolve
That's a little beyond me. Let me back up a sec and maybe you guys can help. I used to use Access to do my data crunching, matching, and cleaning at my old job. I worked with a max of 600k records so Access could handle it. I know, lame, but it's what I knew. I was using Alteryx the past 8

Re: [GENERAL] Problems Importing table to pgadmin

2016-12-07 Thread John R Pierce
On 12/7/2016 3:28 PM, David G. Johnston wrote: On the second image you are using double-quotes to delimit a string literal. This is wrong. PostgreSQL always uses single quotes to indicate literal string value double quotes are reserved for object identifiers (table names, column names, etc).

Re: [GENERAL] Problems Importing table to pgadmin

2016-12-07 Thread metaresolve
Thank you! It was the double quotes. I did run into the permissions error afterwards but I solved it with a google search. Thanks, meta -- View this message in context: http://postgresql.nabble.com/Problems-Importing-table-to-pgadmin-tp5933807p5933812.html Sent from the PostgreSQL - general

Re: [GENERAL] Problems Importing table to pgadmin

2016-12-07 Thread David G. Johnston
On Wed, Dec 7, 2016 at 4:13 PM, metaresolve wrote: > However, when I look at the table it's got the OID fields in there. From > what I read, the default is set to off, so I don't understand why they're > creating them. > >

[GENERAL] Problems Importing table to pgadmin

2016-12-07 Thread metaresolve
Hi, pgAdmin 4 Windows 10 I'm brand new and struggling. I was able to create a table with the CREATE TABLE command and set up the columns. However, when I try to "import" nothing happens, at all. I import the table and hit Ok and nothing happens. If I SELECT * from [table] I get no rows back. I'm