Searched refs:precision (Results 1 – 8 of 8) sorted by relevance
284 precision = -1; in sqlite3_str_vappendf()354 if( precision<0 ){ in sqlite3_str_vappendf()355 precision = precision >= -2147483647 ? -precision : -1; in sqlite3_str_vappendf()411 assert( precision>=(-1) ); in sqlite3_str_vappendf()531 if( precision<0 ) precision = 6; /* Set default precision */ in sqlite3_str_vappendf()543 if( xtype==etGENERIC && precision>0 ) precision--; in sqlite3_str_vappendf()594 precision = precision - exp; in sqlite3_str_vappendf()738 if( precision>1 ){ in sqlite3_str_vappendf()765 && precision<0 in sqlite3_str_vappendf()781 if( precision>=0 ){ in sqlite3_str_vappendf()[all …]
15 # point precision is not high enough to represent their constant integer16 # expression arguments as double precision floating point values.
104 # The precision of the %c conversion causes the character to repeat.
52 # even if the input time-value has millisecond precision.
189 # don't know if we have the precision to manage it from here at this
1583 # Lose of precision when doing comparisons between integer and
3657 # Ticket #1340: Test for loss of precision on large positive exponents
640 # coordinates as single-precision (4-byte) floating point numbers.