|
Hey guys,
As I am transitioning from MySQL, I want to run an issue by you.
In my integer/float/ decimal fields I use functions that create SET
strings or INSERT FIELD and VALUES strings which place single quotes around
the values. So far I have not seen any ill effects from this practice. If
I create an INSERT manually and know I am dealing with a numeric value
going into a numeric field i do not use the single quotes.
But in my functions I do not test or other wise know that the value of
a name => value pair in an associative array is necessarily numeric. As I
said so far, DB2 seems to know that the string I am inserting is a number
and stores it correctly. So in my testing and what I have read, I have not
been very concerned.
But I am creating code that run a financial entity. The more I code
on the i, with PCI compliance in mind, the more I worry about getting
things 100%.
Please let me know I have nothing to worry about...
Thanks
Rob
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.