Positco is returning an incorrect timestamptz than what is being passed in with psycopg2












2















I have a simple script that is passing in a timestamp into a Postgres database. I am viewing the DB with Postico.



I am attempting to pass in a UTC value, by which I mean I want the DB to store all values at +00 timezone. I am using a timestamptz entry in the DB.



On the line prior to writing to the DB, I am printing the value that is being written. The Python console returns:



2018-11-21 10:03:06+00:00



but when I view it on Postico I get:



2018-11-21 11:03:06+01.



Why is Positco returning something different than what is being written? The code is as follows:



import time

import psycopg2

import datetime


def write_to_db(entry):
conn = psycopg2.connect("dbname=testing user=tester")

cur = conn.cursor()
print(entry)
cur.execute("INSERT INTO test (ts) VALUES (%s)", (entry, ))

conn.commit()
cur.close()
conn.close()

def main():
dt = datetime.datetime.utcnow().replace(tzinfo=datetime.timezone.utc).replace(microsecond = 0)
write_to_db(dt)


if __name__ == '__main__':
main()


Edit



Reading from the database returns the following:



(datetime.datetime(2018, 11, 21, 11, 3, 6, tzinfo=psycopg2.tz.FixedOffsetTimezone(offset=60, name=None)),)



So maybe it is an issue with psycopg2 writing to the database?










share|improve this question



























    2















    I have a simple script that is passing in a timestamp into a Postgres database. I am viewing the DB with Postico.



    I am attempting to pass in a UTC value, by which I mean I want the DB to store all values at +00 timezone. I am using a timestamptz entry in the DB.



    On the line prior to writing to the DB, I am printing the value that is being written. The Python console returns:



    2018-11-21 10:03:06+00:00



    but when I view it on Postico I get:



    2018-11-21 11:03:06+01.



    Why is Positco returning something different than what is being written? The code is as follows:



    import time

    import psycopg2

    import datetime


    def write_to_db(entry):
    conn = psycopg2.connect("dbname=testing user=tester")

    cur = conn.cursor()
    print(entry)
    cur.execute("INSERT INTO test (ts) VALUES (%s)", (entry, ))

    conn.commit()
    cur.close()
    conn.close()

    def main():
    dt = datetime.datetime.utcnow().replace(tzinfo=datetime.timezone.utc).replace(microsecond = 0)
    write_to_db(dt)


    if __name__ == '__main__':
    main()


    Edit



    Reading from the database returns the following:



    (datetime.datetime(2018, 11, 21, 11, 3, 6, tzinfo=psycopg2.tz.FixedOffsetTimezone(offset=60, name=None)),)



    So maybe it is an issue with psycopg2 writing to the database?










    share|improve this question

























      2












      2








      2








      I have a simple script that is passing in a timestamp into a Postgres database. I am viewing the DB with Postico.



      I am attempting to pass in a UTC value, by which I mean I want the DB to store all values at +00 timezone. I am using a timestamptz entry in the DB.



      On the line prior to writing to the DB, I am printing the value that is being written. The Python console returns:



      2018-11-21 10:03:06+00:00



      but when I view it on Postico I get:



      2018-11-21 11:03:06+01.



      Why is Positco returning something different than what is being written? The code is as follows:



      import time

      import psycopg2

      import datetime


      def write_to_db(entry):
      conn = psycopg2.connect("dbname=testing user=tester")

      cur = conn.cursor()
      print(entry)
      cur.execute("INSERT INTO test (ts) VALUES (%s)", (entry, ))

      conn.commit()
      cur.close()
      conn.close()

      def main():
      dt = datetime.datetime.utcnow().replace(tzinfo=datetime.timezone.utc).replace(microsecond = 0)
      write_to_db(dt)


      if __name__ == '__main__':
      main()


      Edit



      Reading from the database returns the following:



      (datetime.datetime(2018, 11, 21, 11, 3, 6, tzinfo=psycopg2.tz.FixedOffsetTimezone(offset=60, name=None)),)



      So maybe it is an issue with psycopg2 writing to the database?










      share|improve this question














      I have a simple script that is passing in a timestamp into a Postgres database. I am viewing the DB with Postico.



      I am attempting to pass in a UTC value, by which I mean I want the DB to store all values at +00 timezone. I am using a timestamptz entry in the DB.



      On the line prior to writing to the DB, I am printing the value that is being written. The Python console returns:



      2018-11-21 10:03:06+00:00



      but when I view it on Postico I get:



      2018-11-21 11:03:06+01.



      Why is Positco returning something different than what is being written? The code is as follows:



      import time

      import psycopg2

      import datetime


      def write_to_db(entry):
      conn = psycopg2.connect("dbname=testing user=tester")

      cur = conn.cursor()
      print(entry)
      cur.execute("INSERT INTO test (ts) VALUES (%s)", (entry, ))

      conn.commit()
      cur.close()
      conn.close()

      def main():
      dt = datetime.datetime.utcnow().replace(tzinfo=datetime.timezone.utc).replace(microsecond = 0)
      write_to_db(dt)


      if __name__ == '__main__':
      main()


      Edit



      Reading from the database returns the following:



      (datetime.datetime(2018, 11, 21, 11, 3, 6, tzinfo=psycopg2.tz.FixedOffsetTimezone(offset=60, name=None)),)



      So maybe it is an issue with psycopg2 writing to the database?







      python timestamp psycopg2 timestamp-with-timezone postico






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 21 '18 at 10:07









      mypythonquestionsmypythonquestions

      237




      237
























          0






          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53409626%2fpositco-is-returning-an-incorrect-timestamptz-than-what-is-being-passed-in-with%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53409626%2fpositco-is-returning-an-incorrect-timestamptz-than-what-is-being-passed-in-with%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          這個網誌中的熱門文章

          Xamarin.form Move up view when keyboard appear

          Post-Redirect-Get with Spring WebFlux and Thymeleaf

          Anylogic : not able to use stopDelay()