PostgreSQL issue with mixed case column names

[Anthony_Messina]

I just realized why I was having issues with my Wiki–in PostgreSQL,
column names like wiki_rate_viewLimit, must be quoted

CREATE TABLE egw_wiki_rate
(
wiki_rate_ip character varying(40) NOT NULL DEFAULT ‘’::character varying,
wiki_rate_time integer,
“wiki_rate_viewLimit” smallint,
“wiki_rate_searchLimit” smallint,
“wiki_rate_editLimit” smallint,
CONSTRAINT egw_wiki_rate_pkey PRIMARY KEY (wiki_rate_ip )
)
WITH (
OIDS=FALSE
);
ALTER TABLE egw_wiki_rate
OWNER TO egroupware;

Then things work again

–
Anthony - http://messinet.com - http://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E

[Ralf_Becker_Stylite]

Hi Anthony,

not sure I understand what your problem is.

We recently introduced a fix to automatic quote mixed case column-names
for PostgreSQL and removed manual quotes in code:

http://svn.stylite.de/viewvc/egroupware?view=revision&revision=38307

We tested here two cases:

• new code working with existing wiki tables
• new code can create new tables and workes with them

So, what exactly is failing for you and is your installation up to date?

Ralf

I just realized why I was having issues with my Wiki–in PostgreSQL,
column names like wiki_rate_viewLimit, must be quoted

CREATE TABLE egw_wiki_rate
(
wiki_rate_ip character varying(40) NOT NULL DEFAULT ‘’::character varying,
wiki_rate_time integer,
“wiki_rate_viewLimit” smallint,
“wiki_rate_searchLimit” smallint,
“wiki_rate_editLimit” smallint,
CONSTRAINT egw_wiki_rate_pkey PRIMARY KEY (wiki_rate_ip )
)
WITH (
OIDS=FALSE
);
ALTER TABLE egw_wiki_rate
OWNER TO egroupware;

Then things work again

---

Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev

---

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

–
Ralf Becker
Director Software Development

Stylite AG

Morschheimer Strasse 15 | Tel. +49 6352 70629 0
D-67292 Kirchheimbolanden | Fax. +49 6352 70629 30

Email: rb@stylite.de

www.stylite.de | www.egroupware.org

Managing Directors: Andre Keller | Ralf Becker | Gudrun Mueller
Chairman of the supervisory board: Prof. Dr. Birger Leon Kropshofer

VAT DE214280951 | Registered HRB 31158 Kaiserslautern Germany

---

Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev

---

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

[Anthony_Messina]

Hi Anthony,

not sure I understand what your problem is.

We recently introduced a fix to automatic quote mixed case column-names
for PostgreSQL and removed manual quotes in code:

http://svn.stylite.de/viewvc/egroupware?view=revision&revision=38307

We tested here two cases:

• new code working with existing wiki tables
• new code can create new tables and workes with them

So, what exactly is failing for you and is your installation up to date?

Ralf

I was getting a wiki_rate_searchLimit – no such column PostgreSQL
error. It appears that EGW was creating the query correctly, but I
found in the DB that my column names were lower-cased, probably from
something missed in an earlier setup/upgrade.

Once I manually changed the wiki_rate_{edit,search,view}Limit columns to
have the proper case in the DB, all was well again. I only brought it
up as a matter of “good reporting” in case something might be amiss.

I’m running trunk@38752. I’m guessing a fresh install would not see
this issue.

Thanks again Ralf. -A

–
Anthony - http://messinet.com - http://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E