SQLiteAdapter
Related Doc:
package adapters
unused at the moment, since all jdbc drivers adhere to the standard that : 1 == true, false otherwise.
unused at the moment, since all jdbc drivers adhere to the standard that : 1 == true, false otherwise. If a new driver would not adhere to this, the call can be uncommented in method convertToJdbcValue
unused for the same reason as def convertFromBooleanForJdbc (see comment)
unused for the same reason as def convertFromBooleanForJdbc (see comment)
Converts field instances so they can be fed, and understood by JDBC will not do conversion from None/Some, so @arg r should be a java primitive type or a CustomType
Converts field instances so they can be fed, and understood by JDBC will not do conversion from None/Some, so @arg r should be a java primitive type or a CustomType
Some methods like 'dropTable' issue their statement, and will silence the exception.
Some methods like 'dropTable' issue their statement, and will silence the exception. For example dropTable will silence when isTableDoesNotExistException(theExceptionThrown). It must be used carefully, and an exception should not be silenced unless identified.
This will create an probabilistically unique string of length no longer than 11 chars, it can be used to create "almost unique" names where uniqueness is not an absolute requirement, is not ,
This will create an probabilistically unique string of length no longer than 11 chars, it can be used to create "almost unique" names where uniqueness is not an absolute requirement, is not ,
Figures out from the SQLException (ex.: vendor specific error code) if it's cause is a NOT NULL constraint violation
Figures out from the SQLException (ex.: vendor specific error code) if it's cause is a NOT NULL constraint violation
When @arg printSinkWhenWriteOnlyMode is not None, the adapter will not execute any statement, but only silently give it to the String=>Unit closure
When @arg printSinkWhenWriteOnlyMode is not None, the adapter will not execute any statement, but only silently give it to the String=>Unit closure
Should we verify that when we delete by primary key the JDBC driver reports that no more than one row was affected? MonetDB in particular seems to act badly here
Should we verify that when we delete by primary key the JDBC driver reports that no more than one row was affected? MonetDB in particular seems to act badly here
true if we should throw an exception if the driver reports more than 1 affected row