Re: [pgadmin-support] "Runtime Error 55 File Already Open" after clicking the Databases in the tree
Is it possible for you to try installing pgAdmin 1.3.60? Regards, Dave. > -Original Message- > From: Serkan Bektaþ [mailto:[EMAIL PROTECTED]] > Sent: 24 July 2002 22:05 > To: Dave Page; [EMAIL PROTECTED] > Subject: RE: [pgadmin-support] "Runtime Error 55 File Already > Open" after clicking the Databases in the tree > > > > I don't have any new databases on the server. > > Recent changes I remember are > --- > * MDAC installation. > * Datanamic - Database Design Made Easy with DeZign for > databases (this tool does not connect to the database, only > generates SQL scripts) > ( http://www.datanamic.com/dezign/index.html ) > > > Regards, > Serkan Bektas > > > > -Original Message- > From: Dave Page [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, July 24, 2002 10:51 PM > To: Serkan Bektaþ; [EMAIL PROTECTED] > Subject: RE: [pgadmin-support] "Runtime Error 55 File Already > Open" after clicking the Databases in the tree > > > > > > -Original Message- > > From: Serkan Bektaþ [mailto:[EMAIL PROTECTED]] > > Sent: 24 July 2002 21:43 > > To: Dave Page; [EMAIL PROTECTED] > > Subject: RE: [pgadmin-support] "Runtime Error 55 File Already Open" > > after clicking the Databases in the tree > > > > > > Hi Dave, > > > > re-installed pgadmindid not solve, > > re-installed psqlODBC-did not solve, > > installed MDAC 2.6 --did not solve, > > > > full log files attached > > Do you have any new databases on the server, or have there > been any other recent changes you can think of? > > Regards, Dave. > > ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[pgadmin-support] Problem with pgadmin II and psql
Hi, First I create a database in psql, not in PgAdmin. After, when I create a table in PgAdmin it's not accessible in psql but if I create it in psql, it works, it's accessible in PgAdmin but not modifiable (I can't change the column name or drop the column). When I create a table or a column with PGAdmin, I must always use the quoted delimiters to access it the table and the columns. I don't find an option who can be changed to say to PgAdmin that it don't use the double-quote. Does anybody have an idea ? Stef -- http://www.ecolo.be ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [pgadmin-support] Problem with pgadmin II and psql
You probably used CAPITALS - I also had this problem - it's not a bug, it's a feature ;) I would appreciate PgAdmin using the non-quoted mode for creating objects - or at least be user configurable, because this non SQL conformant feature confuses many users (I think). Best regards, Maxx -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im Auftrag von ROUWEZ Stephane Gesendet: Donnerstag, 25. Juli 2002 13:42 An: '[EMAIL PROTECTED]' Cc: LESNE Philippe Betreff: [pgadmin-support] Problem with pgadmin II and psql Hi, First I create a database in psql, not in PgAdmin. After, when I create a table in PgAdmin it's not accessible in psql but if I create it in psql, it works, it's accessible in PgAdmin but not modifiable (I can't change the column name or drop the column). When I create a table or a column with PGAdmin, I must always use the quoted delimiters to access it the table and the columns. I don't find an option who can be changed to say to PgAdmin that it don't use the double-quote. Does anybody have an idea ? Stef -- http://www.ecolo.be ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [pgadmin-support] Problem with pgadmin II and psql
> -Original Message- > From: ROUWEZ Stephane [mailto:[EMAIL PROTECTED]] > Sent: 25 July 2002 12:42 > To: [EMAIL PROTECTED] > Cc: LESNE Philippe > Subject: [pgadmin-support] Problem with pgadmin II and psql > > > Hi, > > First I create a database in psql, not in PgAdmin. > After, when I create a table in PgAdmin it's not accessible > in psql but if I create it in psql, it works, pgAdmin will quote the identifiers in case you use mixed case (1.3.60 will only quote them if required), psql will not. So, if you create a table called MyTable in pgAdmin, from psql you must manually quote: SELECT * FROM "MyTable" The easiest option is to use lowercase names with no special characters other than _ in them. > it's accessible > in PgAdmin but not modifiable (I can't change the column name > or drop the column). You can rename columns by selecting the Column properties from the treeview, *not* in the Table properties. PostgreSQL cannot yet drop columns, hence neither can pgAdmin. > When I create a table or a column with > PGAdmin, I must always use the quoted delimiters to access it > the table and the columns. > > I don't find an option who can be changed to say to PgAdmin > that it don't use the double-quote. If you use mixed case names, they *must* be quoted. Stick to lower case and you can lose the quotes. Regards, Dave. ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [pgadmin-support] Problem with pgadmin II and psql
> -Original Message- > From: Markus Brachner [mailto:[EMAIL PROTECTED]] > Sent: 25 July 2002 12:58 > To: ROUWEZ Stephane; [EMAIL PROTECTED] > Cc: LESNE Philippe > Subject: Re: [pgadmin-support] Problem with pgadmin II and psql > > > You probably used CAPITALS - I also had this problem - it's > not a bug, it's a feature ;) I would appreciate PgAdmin using > the non-quoted mode for creating objects - or at least be > user configurable, Current development versions of pgAdmin will only use quotes where required, though this still leaves you with the "problem" that if you create a table called MyTable it is MyTable and not mytable. > because this non SQL conformant feature > confuses many users (I think). If PostgreSQL (note, *not* pgAdmin) followed the spec, then this problem would still remain. To quote from the spec, and Tom Lane: >>> 13)A and a are equiva- lent if the of the (with every letter that is a lower-case letter replaced by the equiva- lent upper-case letter or letters) and the of the (with all occurrences of replaced by and all occurrences of replaced by ), considered as the repetition of a that specifies a of SQL_TEXT and an implementation- defined collation that is sensitive to case, compare equally according to the comparison rules in Subclause 8.2, "". The spec expects unquoted identifiers to be made case-insensitive by folding them to upper case. We do it by folding to lower case, instead. While this isn't 100% standard, it's unlikely to be changed. Too many applications would break... >>> In other words, you would still get the case where MyTable != mytable != MYTABLE. Regards, Dave. ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
