Uhu. Aha.
bax
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3836876#3836876
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3836876
---
This SF.Net email is sponsored
Thanks for your kind reply :)))
Mhhhm, i do not see an end here either.
The Java vs. DB NULL problem is an chicken-and-egg problem. The NULL in the DB is not
the Java NULL, so it must be converted in both directions. That for you have to test
if it is NULL. Circle closed.
Do you have the full
I apologize.
Let's bring this social NPE to an end:
I apologize too for sounding anything else than helping. I neither know what
revendicative in German is [babelfish and dict.leo.org doesn't help here] nor does I
know _how_ to write or say something that it is sounding condescending in
revendicative means claiming your truth at the expense of those of others
This forum is for helping each other to make everyone find its truth (means the way
where its application works). Blaming J2EE, JBoss, ER designers or ER models got
nothing to do with this forum.
So, finallly, make a
Thanks.
Then I apologize for sounding revendicative. Never want to draw upon the objective
truth, know that this is not existing. My truth is simply my truth, not more - but not
less.
bax
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3836628#3836628
Reply
hbaxmann:
Thank you for posting the message with kinder English and approaching it technically
without commenting on a person's skill levels. I apologize if I was harsh on your
choice of words, or use of English.
I'll respond to the technical notions in your post now as best I can.
anonymous wrote : This isn't a relational issue.
Right, because in this kind of usage your Entity design simply lacks. This solution is
a workaround. In most cases one is not able to tidy up, normalize an already
implemented ER model.
The one and only solution is to have a 3rd NF ER model -
hbaxmann:
You are clearly learning relational theory in an academic setting. What school are
you attending? What is your major?
For one, no one completely normalizes data in the real world, and by real world, I
mean business applications. When someone does, it's clear it's a college student
nice to meet you, too
bax
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3836534#3836534
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3836534
---
This SF.Net email is
You are too much revendicative to exchange with both of you. When you want to justify
yourself so much, it's suspect for me. Continue to consider everyone as newbie while
you seems to stand yourself on some cloud, nobody's care.
Nice to meet you too, but not too much !
View the original post
ironbird:
You're right. And I do apologize for coming off as condescening.
Believe me, though, it has nothing to do with his being a newbie. I am normally very
supportive of people learning something new.
His tone was condescending, so I felt he needed to hear himself in context.
??? What do you say ?
You can get null values rows in EJB-QL testing by IS NULL.
For example the EJB-QL query
| * @ejb.finder
| * view-type=remote
| * signature=java.util.Collection
findCustomers(Pharma_EJB.interfaces.Pharma_Customer customer)
| * query=SELECT DISTINCT OBJECT(c)
The problem with that query is that it will return rows where c.customer IS NULL but
the parameter ?1 is not null. You only want rows where c.customer is null and ?1 is
also null. The equals doesn't work, and IS NULL only tests one side of the equation.
You can't apply it to the parameter to
anonymous wrote : Path expression navigability is composed using ?inner join?
semantics. That is, if the value of a non-terminal cmr-field in the path expression is
null, the path is considered to have no value, and does not participate in the
determination of the result.
|
If that's the
You can do what you want with DynamicSQL, which is specific to JBoss. But the J2EE
spec do not address your needs.
Even in any language (PL-SQL, T-SQL, C++ or whatever), you need to build dynamically
your SQL string to do what you want.
Why do you want the container do the job for you ?
View
anonymous wrote :
| Why do you want the container do the job for you ?
|
Because I am using container managed persistence (CMP) and EJB-QL is a the Query
Language?
Are you asking why I'm using container managed persistence?
| - To obtain database vendor indepedence. The
anonymous wrote :
| Because I am using container managed persistence (CMP) and EJB-QL is a the Query
Language?
|
EJB-QL query is for persistence with additional features, not complex queries. I agree
with you that the spec is not adapted with professional applications. I work in
industry
IMHO there is no big, but fundamental problem:
- if your app rely on more then one _significant_ optional field - your ER model sucks
- NULL compared to anything gives false, even NULL=NULL
solution: build a db view per optional field, null-'key' rows will vanish, not the
denormalized table
hbaxmann:
anonymous wrote : solution: build a db view per optional field, null-'key' rows will
vanish, not the denormalized table
This isn't a relational issue. The query I mentioned with 4 columns ironically has no
relationships whatsoever. However, it does have 4 optional columns I need
hbaxmann:
anonymous wrote : solution: build a db view per optional field, null-'key' rows will
vanish, not the denormalized table
This isn't a relational issue. The query I mentioned with 4 columns ironically has no
relationships whatsoever. However, it does have 4 optional columns I need
20 matches
Mail list logo
