Oracle has these pesky semantics of conflating NULL and the empty
string. Added a comment on the bug.
--a.
Ron Peterson wrote:
2008-12-01_11:21:11-0500 rpeterso:
2008-11-28_07:32:00-0500 Dick Davies <[EMAIL PROTECTED]>:
I filed a bug about this earlier in the week
https://issues.apache.org/roller/browse/ROL-1762
Seems like another JPA/Oracle issue.
In a nutshell; if you submit a comment with the 'name' field left blank,
the 'name' field in the database ends up NULL.
The roller 'comment' admin screen chokes on this later
(Freemarker gives 3 enormous stacktraces instead of checkboxes).
I'm not sure if it's a FreeMarker or JPA bug; does anyone else see it?
I suspect this is another 'fine on mysql' thing, so be good if some postgresql
people could verify it.
Hi Dick,
I'm using Roller 4.0.1 on PostgreSQL 8.3. I just tried submitting a
comment with no name, and had no problem on the admin screen. I'll try
a few more variations to see if I can recreate this.
My test user was a global admin. I removed global admin privs, but
still works fine.
I'm not getting nulls in the name field of my roller_comment table.
pubtest=> select * from roller_comment where name is null order by posttime;
LOG: statement: select * from roller_comment where name is null order by
posttime;
(No rows)
This is not due to a database constraint/rule/trigger that I can see.
Table "public.roller_comment"
Column | Type | Modifiers
-------------+--------------------------+--------------------------------------------------
id | character varying(48) | not null
entryid | character varying(48) | not null
name | character varying(255) |
...
HTH.
