Re: EJB3/JPA with Oracle
Hugh Allen <[email protected]> Tue, 29 Jul 2014 13:43:30 -0400 (GMT-04:00)
| Newsgroups | gmane.org.user-groups.trijug.juglist |
|---|---|
| Message-ID | <25634992.1406655810891.JavaMail.root@elwamui-rubis.atl.sa.earthlink.net> |
--===============0247748699045985340==
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8
<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-size: 13px;color: rgb(0, 0, 0);font-family: ari=
al, sans-serif;">DOUBLING the size of the database??? <span style=3D"f=
ont-size: 10pt;">This seems a non-starter.</span><div><br></div><div>So bas=
ically, Oracle was written in 197X or so - I was around at the time - EVERY=
THING was in CAPS - all mainframe data.</div><div><br></div><div>I did my M=
BA Thesis in 1974 on a mainframe on a 3270 green terminal at Merrill Lynch,=
where I was working, ALL IN CAPS. Had to explain why I had not used a TYPE=
WRITER.</div><div><br></div><div>Looks like Oracle is still in 1974. They e=
xpect us to load everything in the database in UPPER CASE?</div><div><br></=
div><div>This cross-database stuff is harder than it looks. JPA doesn't han=
dle this in any way, with ORACLE, which is THE major database?</div><div><b=
r></div><div>MySQL was easy. SQL Server only minor issues. Oracle is a nigh=
tmare of old landmines from the 70s.</div><div><br></div><div>What am I mis=
sing?</div><div><br></div><div>Hugh<br><br><blockquote style=3D"padding-lef=
t: 5px; margin-left: 0px; border-left: #0000ff 2px solid; font-weight: norm=
al; font-style: normal; text-decoration: none; font-size: 10pt; font-family=
: arial,sans-serif; color: black;">-----Original Message-----
<br>From: Olaf Luetkehoelter <[email protected]>
<br>Sent: Jul 29, 2014 10:11 AM
<br>To: Hugh Allen <[email protected]>
<br>Cc: [email protected]
<br>Subject: Re: [Juglist] EJB3/JPA with Oracle
<br><br><zzzhtml><zzzhead><zzzmeta http-equiv=3D"Content-Type" content=3D"t=
ext/html charset=3Dus-ascii"></zzzmeta></zzzhead><zzzbody style=3D"word-wra=
p: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-sp=
ace;">A common way of implementing case insensitive search (and avoid full =
table scans) in Oracle is to add another column for each column that you wa=
nt to search on, copy the to_upper() values of your original fields into th=
e new column, add indexes on the new columns and use to_upper in your selec=
t statements.<div><br></div><div>thanks,</div><div>Olaf<br><div><i style=3D=
"font-family: 'Lucida Handwriting'; orphans: 2; text-align: -webkit-auto; w=
idows: 2;">---</i><div apple-content-edited=3D"true"><div style=3D"color: r=
gb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: nor=
mal; font-weight: normal; letter-spacing: normal; line-height: normal; orph=
ans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; w=
hite-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust:=
auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-=
mode: space; -webkit-line-break: after-white-space; "><div><font face=3D"Lu=
cida Handwriting"><i>Olaf Luetkehoelter</i></font></div><div><font face=3D"=
Lucida Sans"><a target=3D"_blank" href=3D"mailto:[email protected]">[email protected]=
.com</a></font></div><div><font face=3D"Lucida Sans">919-727-6523</font></d=
iv></div>
</div>
<br><div><div>On Jul 29, 2014, at 08:37 , Hugh Allen <<a target=3D"_blan=
k" href=3D"mailto:[email protected]">[email protected]</a>>=
; wrote:</div><br class=3D"Apple-interchange-newline"><blockquote type=3D"c=
ite">Hi,<br><br>Hope we have some Oracle/JPA experts out there, because Goo=
gle searches are not showing me the answer.<br><br>After using MySQL and SQ=
L Server exclusively for years, we are now porting our Java EJB3/JPA app to=
Oracle, based on requirements from a client.<br><br>Thought this would be =
a snap but no such luck. Oracle OWNS Java, for crying out loud. How hard co=
uld this be???<br><br>So I guess this is an Oracle newbie question.<br><br>=
1) Resolved the 30 character limit on column names by changing JPA<br><br>2=
) Resolved Oracle's inability to distinguish between NULL and Empty String.=
(Oracle calls an Empty String an IMPOSSIBLE VALUE! But in fact it is very =
possible and the DEFAULT in the app, which has NOT NULL for all strings.)<b=
r><br>3) But now *CASE SENSITIVE Queries* are the problem. By default all O=
racle queries are Case Sensitive! This is a ridiculous default, and there m=
ust be some way around it???<br><br>Discovered there is an Oracle setting f=
or NLS_COMP but this is a SESSION parameter and JPA can not control Oracle =
Sessions? How can this be accomplished?<br><br>Guessing many of you use Ora=
cle. Any help on setting up Case IN-SENSITIVE searches in Oracle?<br><br>Wi=
thout changing all the queries to use LOWER()?<br><br>Thanks, Hugh<br><br><=
br><br><br><br>_______________________________________________<br>Juglist m=
ailing list<br><a target=3D"_blank" href=3D"mailto:[email protected]=
">[email protected]</a><br>http://lists.trijug.org/mailman/listinfo/=
juglist_lists.trijug.org<br></blockquote></div><br></div></div></zzzbody></=
zzzhtml></[email protected]></[email protected]></blockquote></div></di=
v></body></html>
--===============0247748699045985340==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Juglist mailing list
[email protected]
http://lists.trijug.org/mailman/listinfo/juglist_lists.trijug.org
--===============0247748699045985340==--