<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Simba ODBC datetime with millisecond overflows in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/simba-odbc-datetime-with-millisecond-overflows/m-p/14943#M9349</link>
    <description>&lt;P&gt;I was passing a string (e.g. '2022-07-03 13:57:48.500') to the Golang SQL driver which is not working if the ms part is specified, but otherwise it works (e.g. '2022-07-03 13:57:48'). Passing a native Golang time.Time seems to work for timestamps with a ms part too.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your help.&lt;/P&gt;</description>
    <pubDate>Fri, 08 Jul 2022 06:54:54 GMT</pubDate>
    <dc:creator>158808</dc:creator>
    <dc:date>2022-07-08T06:54:54Z</dc:date>
    <item>
      <title>Simba ODBC datetime with millisecond overflows</title>
      <link>https://community.databricks.com/t5/data-engineering/simba-odbc-datetime-with-millisecond-overflows/m-p/14939#M9345</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using odbc 2.6.24.1041-2 for Linux, when inserting rows with milliseconds precision date (e.g. 2022-07-03 13:57:48.500) precision I get:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2022/07/03 14:41:19 SQLExecute: {22008} [Simba][Support] (40520) Datetime field overflow resulting from invalid datetime.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With Scala works fine:&lt;/P&gt;&lt;P&gt; spark.sql("INSERT INTO ... () VALUES ('2022-07-03 13:57:48.500')");&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way to add millisecond precision with ODBC (or JDBC which I've not tried yet)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Nikos&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 03 Jul 2022 14:49:12 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/simba-odbc-datetime-with-millisecond-overflows/m-p/14939#M9345</guid>
      <dc:creator>158808</dc:creator>
      <dc:date>2022-07-03T14:49:12Z</dc:date>
    </item>
    <item>
      <title>Re: Simba ODBC datetime with millisecond overflows</title>
      <link>https://community.databricks.com/t5/data-engineering/simba-odbc-datetime-with-millisecond-overflows/m-p/14941#M9347</link>
      <description>&lt;P&gt;Hi @Nikos Mitsis​&amp;nbsp;have you tried `CAST()`&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jul 2022 10:55:43 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/simba-odbc-datetime-with-millisecond-overflows/m-p/14941#M9347</guid>
      <dc:creator>Prabakar</dc:creator>
      <dc:date>2022-07-07T10:55:43Z</dc:date>
    </item>
    <item>
      <title>Re: Simba ODBC datetime with millisecond overflows</title>
      <link>https://community.databricks.com/t5/data-engineering/simba-odbc-datetime-with-millisecond-overflows/m-p/14943#M9349</link>
      <description>&lt;P&gt;I was passing a string (e.g. '2022-07-03 13:57:48.500') to the Golang SQL driver which is not working if the ms part is specified, but otherwise it works (e.g. '2022-07-03 13:57:48'). Passing a native Golang time.Time seems to work for timestamps with a ms part too.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your help.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Jul 2022 06:54:54 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/simba-odbc-datetime-with-millisecond-overflows/m-p/14943#M9349</guid>
      <dc:creator>158808</dc:creator>
      <dc:date>2022-07-08T06:54:54Z</dc:date>
    </item>
  </channel>
</rss>

