Re: INSERT Column Type Conversions

I know what values are going into the fields... my MakeSets and MakeInsert functions have not a clue, so not matter what , all values are inside single quotes....

I have already validated the data... it all sets in an associative array. I then send the array to one of my functions and turn it into:

$sfields = '"Field1", "Field2", "Field3"' ;
$sValues = "'Value1', 'Value2', 'Value3'" ;

To be used like: 'INSERT INTO TABLE ( ' . $sFields . ' ) VALUES ( ' . $sValues . ' ) ;' ;

OR

$sSets = '"Field1" = \'1\', "Field2" = \'String\', "Field3" = \'41576\'' ;

To Be Used Like: 'UPDATE TABLE SET ' . $sSets . ' WHERE ID = 10 ;' ;

My functions are in my previous message....



On 01/19/2016 04:46 PM, John Yeung wrote:

On Tue, Jan 19, 2016 at 12:26 PM, Rob <rob.couch@xxxxxxxxxxxxxx> wrote:

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.

Then no doubt DB2 is attempting to coerce the values it receives into
the appropriate type for storage in the table, and if it succeeds,
then it quietly continues processing.

What I'm a little confused about actually is that you don't know the
types of the values. You said you're using PHP, which is among the
most weakly typed languages out there; but nevertheless, it has
type-testing functions (like gettype(), is_numeric(), and so forth).
If you care about the types, why can't you just use those functions in
your code?

John Y.