230 reputation
26
bio website jeffkemponoracle.com
location Perth, Australia
age 39
visits member for 4 years
seen May 7 at 6:30

Oracle Database Designer and Developer

Since 2000 Jeffrey has designed, developed, maintained and enhanced a variety of large and small custom applications for the government sector using Oracle Database 7.3, 8i, 9i, 10g and 11g; Application Express 3.1, 3.2, 4.0, 4.1, and 4.2; Oracle Forms 4.5, 6i, 9i and 10g; Oracle Reports 2.5, 6i and 9i.

He has particular interests and experience in Oracle SQL, PL/SQL, database performance tuning, and Oracle Application Express (APEX).


Apr
28
comment Designing XML - confused between attributes and elements
Yes, you said that in your question. I'm just pointing out that hardcoding that assumption into your design now may prove to be a limiting factor in the future; whereas a more general design (one that allows combining different payment types in the same document) may be better in the long run. BUT, you know your system better than me.
Apr
28
comment Designing XML - confused between attributes and elements
In your particular example, the attributes seem to be describing each individual PAYMENT, rather than the whole body of PAYMENTS so it doesn't make sense to have them at that level - what if one payment happens to be a different payment type or currency? Anyway, personally I'd make the currency and payment type as additional elements on each payment - that way each payment is a self-contained entity, and may be easier to parse (IMHO). Imagine if you wanted to combine two sets of payments into one - it would not work unless both had the same currency and paymenttype.
Apr
28
comment Designing XML - confused between attributes and elements
And: stackoverflow.com/questions/33746/xml-attribute-vs-xml-element
Apr
28
comment Designing XML - confused between attributes and elements
Check out this q: stackoverflow.com/questions/241819/…
Apr
24
comment Learning to investigate bugs
Read Pirsig's Zen And The Art Of Motorcycle Maintenance amazon.com/Zen-Art-Motorcycle-Maintenance-Inquiry/dp/0060589469
Apr
16
comment How to make sure that reported issues are not caused by wrong credentials or typos of the client?
I generally walk over there, tell them I'm having trouble reproducing the problem, and ask pretty please ("sorry for the trouble", etc. etc.) show me again. 50% of the time it's "oh, it's working now! You fixed it!" and the bug is closed. This is why I never take more than an hour to reproduce an issue - if I can't reproduce it in an hour I go back to the client.