Quote:
Hi, this is the code I'm using in DBDelete - hardcoded to avoid issues:
NpgsqlCommand CMD = new NpgsqlCommand("DROP DATABASE \"HoldemManagerBeta\"", CONN);
CMD.ExecuteNonQuery();
Not sure why the logging is saying something different? You seem to know quite a bit about Postgres so I'd be happy to provide any more info to get to the bottom of this.
I doubt I know enough to help but will just say that I open a terminal to monitor the log as I clicked "delete database" and what I pasted in is what showed up in the terminal. Repeated about a dozen times every 5s before hem posted its error 'can't delete db' dialog.
I will up logging a little to see what else it reveals but I don't think I'll see much more; it could be an issue with "^M" but I can't simulate that myself. I assume the other poster is running pgsql locally so there could be more than one issue w/the "delete" (or a single issue where the cmd/args are just plain wrong; really don't know. Mine is pgsql 8.2.3 if it matters).
TBH you seem like a very hard-working, conscientious and ambitious guy but I really only wanted to see what all the fuss was about w/hem and at this point will probably just wait until you go golden and take a look then.
Quote:
Edit: And I;ve found with a few people that not having a "postgres" user name seemed to cause issues with DB creation.
I do have a user postgres, just not local to xp. I run xp in vmware w/pgsql on linux and I doubt xp is calling him "postgres"; I'd guess something like "\localhost
ostgres" or something like that. But not being a windows user I don't really know; that's just that sort of thing I see when xp refers to remote discs.
Or the problem is that my xp login name has some appendage added to it by hem/xp such that linux pgsql doesn't recognize that xp user as a member of postgres group. Just a guess; but there is definitely a "postgres" user and a "postgres" group at the linux pgsql.