I'm using this script with and moment-timezone.js: time zone - not your own. If you are unsure, you can always test it out by changing your local computer's clock to just before the DST change for wherever you're located and see what happens.
I would like it to return dates on date boundaries and time at noon.#ln -sf /usr/share/Below is the output after I made the change and continued the 16.04 dist-upgrade process. After this operation, 142 MB of additional disk space will be used. [Y/n] Extracting templates from packages: 100% Preconfiguring packages ... Current default time zone: ' Etc/UTC' Local time is now: Sun Mar 13 UTC 2016. Run 'dpkg-reconfigure tzdata' if you wish to change it. 398777 files and directories currently installed.) Preparing to unpack .../python- /etc/timezone [email protected]# dpkg-reconfigure -f noninteractive tzdata [email protected]# cat /etc/timezone Etc/UTC And nothing will be happened. I suppose that it is a tzdata package bug in 16.04.820 upgraded, 17 newly installed, 3 to remove and 144 not upgraded. https://developer.tizen.org/dev-guide/web/2.3.0/org.tizen.device.apireference/tizen/This API can be used to get TZDate objects with full time zone support, convert them between timezones, retrieve available timezones. The usage scenarios could be much broader than what is mentioned but yes, basically more flexibility in dealing with relative dates, DST settings etc. One difference I have noticed between both is that the Tizen date object (get Current Date Time()) is "synchronized" with the date object on a companion app running on your paired smartphone.For example, whenever the timezone changes on the smartphone the tizen date object reflects this change whilst the date() function does not reflect this.It looks like this: Query: ``` SELECT r.request_id, usr_actual_start_date date_date, TO_CHAR( w.usr_actual_start_date, ' DD. YYYY HH24: MI: SS' ) char_date, dump(usr_actual_start_date) dump_date FROM requests r ``` Oracle SQL Developer with JDBC driver: ! See https://oracle.github.io/odpi/doc/for help ``` The version of instant client installed is a bit old: ``` (venv) (python27)[[email protected] ~]$ rpm -qa|grep instant oracle-instantclient11.2-basic-126.96.36.199.0-1.x86_64 oracle-instantclient11.2-devel-188.8.131.52.0-1.x86_64 (venv) (python27)[[email protected] ~]$ rpm -ql oracle-instantclient11.2-basic-184.108.40.206.0-1.x86_64|grep libclnt /usr/lib/oracle/11.2/client64/lib/11.1 ``` The obvious way to fix this is to extend LD_LIBRARY_PATH: ``` $ LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/oracle/11.2/client64/lib python -c "import cx_Oracle; print cx_Oracle.version" 6.0b1 ``` For easing the upgrade to users of cx_Oracle it would make sense though to keep the behaviour to guess the instant client installations like did for cx_Oracle 5.3. OBJECT' object has no attribute 'read' ```python result = cursor.execute( """SELECT XMLElement("Date", hire_date) FROM hr.employees WHERE employee_id = 203""" ) for res in result: # The exception occours right here raw_xml = res.read() ``` But there are simple workaround.