Page 1 of 1
About Question enthuware.oce-jpad.v6.2.347 :
Posted: Mon Jan 02, 2012 11:04 am
by ETS User
There is case-sensitive problem in this question, for exemple:
- columnB: wrong
- COLUMB: correct
Re: About Question enthuware.oce-jpad.v6.2.347 :
Posted: Mon Jan 02, 2012 3:44 pm
by admin
You are right. This has now been fixed.
Thank you for your feedback!
Re: About Question enthuware.oce-jpad.v6.2.347 :
Posted: Thu Mar 22, 2012 10:40 pm
by Guest
This is not fixed yet, I'm using version 1/11.
Re: About Question enthuware.oce-jpad.v6.2.347 :
Posted: Fri Mar 23, 2012 5:17 am
by admin
Guest wrote:This is not fixed yet, I'm using version 1/11.
Probably I am missing something but I don't see any case mismatch. Attached is the view that I see. Could you please let me know what do you think is wrong?
Re: About Question enthuware.oce-jpad.v6.2.347 :
Posted: Fri Mar 23, 2012 11:45 am
by durgeshagrawal
the problem is with field v/s FIELDD
Re: About Question enthuware.oce-jpad.v6.2.347 :
Posted: Fri Mar 23, 2012 11:46 am
by Guest
It is treating fieldD and FIELDD differently
Re: About Question enthuware.oce-jpad.v6.2.347 :
Posted: Fri Mar 23, 2012 1:08 pm
by admin
But it is clearly mentioned in the problem statement, "Write the names in ALL CAPS".
Re: About Question enthuware.oce-jpad.v6.2.347 :
Posted: Sat Mar 24, 2012 5:30 am
by M_Z
Hi Paul,
I also was puzzled on this question in JPAD by lowecase/uppercase problem.
After a research in internet, I believe that persistence providers will be uppercasing column names (if nothing explicitly defined). So uppercase is correct here. Maybe a red note (write in uppercase comment) must be in bigger font, it's not very noticeable. Or make comparison when you checking answer case-independent.
best regards,
Mikalai Zaikin