This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hello, I use LightSpeed v.5.0.2849.0 and MS SQL 2008. We have a datetime2(7) field in a table. Whenever we insert a record in this table, LS converts the value for datetime field to standard SQL datetime format and thus we lose all the precision of a datetime2(7) field. For example, if we try to insert '2015-03-12 14:56:49.2189038' - LS will insert '2015-03-12 14:56:49.2180000' in this field. So, how can we make LS insert datetime without losing precision? |
|
|
|
|
Because we dont know if the column is a datetime2 or a datetime we bind all SQL datetime range values as that type and any values which would fall outside that range as a datetime2. If you want to explicitly insert or update datetime2's for all values you will need to use a stored procedure.
|
|
|
|
