# timezone Published articles for timezone. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Home Assistant timezone and configuration override issues DevFeed: [Home Assistant timezone and configuration override issues]() Original publisher: [Read original article]() Author: Nicolas Fränkel Published: 2026-07-05T00:00:00Z Content type: opinion Language: en Sources: [Nicolas Fränkel]() Topics: [Home Assistant](), [timezone](), [Automation](), [bug](), [configuration](), [YAML]() Tags: [automation](), [bugs](), [config](), [home-assistant](), [locale](), [technical](), [timezone](), [user-experience](), [yaml]() ### AI overview The author describes Home Assistant shutter automations that ran an hour late during summer time because the instance timezone appeared as Paris/+1. Overriding the timezone in configuration removed UI-set settings, requiring all settings to be specified again in YAML. ### Source excerpt Last year, I motorized the rolling shutters on the southern façade of my apartment. My idea was to manage them via Home Assistant. I had a couple of automations in mind: In the evening, roll down the shutters of my bedroomIn the morning:If it's too hot outside, roll down all shuttersIf it's too cold outside, roll down all shuttersIn other cases, roll up all shutters but my bedroom's Living in France, I added the official Météo France integration. ## New roots, same Square DevFeed: [New roots, same Square]() Original publisher: [Read original article]() Author: Pierre-Yves Ricau Published: 2026-07-02T20:52:29Z Content type: opinion Language: en Sources: [Py's blog]() Topics: [Software Engineering](), [Artificial Intelligence]() Tags: [ai](), [engineering](), [remote](), [software-engineering](), [time](), [timezone](), [work]() ### AI overview The author describes moving from San Francisco back to France while continuing to work for Square remotely. The article discusses the administrative and family considerations behind the move, timezone differences, and how AI-enabled autonomy provides more uninterrupted focus time in software engineering. ### Source excerpt Exactly one year ago, after 12 years in San Francisco, I moved back to France. Life since has been a whirlwind: selling the condo, moving a container overseas, rediscovering French culture (I had to r ## British Columbia, Time Zones, and Postgres DevFeed: [British Columbia, Time Zones, and Postgres]() Original publisher: [Read original article]() Author: Christopher Winslett Published: 2026-06-16T12:00:00Z Content type: tutorial Language: en Sources: [CrunchyData Blog]() Topics: [DateTime](), [Query (disambiguation)](), [Ubuntu]() Tags: [postgres](), [production-postgres](), [sql](), [time](), [timezone](), [ubuntu]() ### AI overview This article explains how British Columbia's permanent move to UTC-7 affects PostgreSQL handling of future appointments and time-zone conversions. It warns that changed time-zone rules or outdated tzdata packages can cause stored appointments to display at the wrong local time. ### Source excerpt This year, British Column has moved to year-round Pacific Time. How does that affect date data? ## How to render timestamp with a timezone that is different from current? DevFeed: [How to render timestamp with a timezone that is different from current?]() Original publisher: [Read original article]() Author: depesz Published: 2026-01-27T09:25:04Z Content type: tutorial Language: en Sources: [select \* from depesz;]() Topics: [timezone](), [PostgreSQL](), [DateTime]() Tags: [formatting](), [how-to](), [irc](), [postgresql](), [timestamptz](), [timezone](), [to-char](), [uncategorized](), [utc]() ### AI overview A PostgreSQL tutorial explaining why timestamptz values are displayed in the client's local timezone and how to render a timestamp with an offset for another timezone. It presents a custom function that returns text, preserves the client timezone, and optionally applies to_char formatting. ### Source excerpt This question appeared on IRC, and while I wasn't there while it happened, it caught my eye: " Can I not render this with timezone offset: select '2026-01-09 04:35:46.9824-08'::timestamp with time zone at time zone 'UTC'; " Returns '2026-01-09 12:35:46.9824' which is without the offset. Let's see what can be done about it. First, let's ... Continue reading "How to render timestamp with a timezone that is different from current?" ## How to map the Oracle TIMESTAMP WITH TIME ZONE with JPA DevFeed: [How to map the Oracle TIMESTAMP WITH TIME ZONE with JPA]() Original publisher: [Read original article]() Author: vladmihalcea Published: 2025-03-18T16:21:37Z Content type: tutorial Language: en Sources: [Vlad Mihalcea]() Topics: [Oracle Database](), [Java](), [SQL]() Tags: [article](), [hibernate](), [how-to](), [java](), [jpa](), [mapping](), [offsetdatetime](), [oracle](), [sql](), [timezone](), [types](), [zoneddatetime]() ### AI overview A tutorial on mapping Oracle TIMESTAMP WITH TIME ZONE columns to Java date-time types using JPA and Hibernate. It explains how ZonedDateTime and OffsetDateTime correspond to the Oracle column type and how to preserve time zone region information when retrieving values. ### Source excerpt Introduction In this article, I'm going to explain how to map the Oracle TIMESTAMP WITH TIME ZONE with JPA and Hibernate. While the DATE and TIMESTAMP column types are suitable for mapping the LocalDateTime, the TIMESTAMP WITH TIME ZONE column type allows us to map both the ZonedDateTime and OffsetDateTime. Oracle TIMESTAMP WITH TIME ZONE Traditionally, Oracle provided the DATE and TIMESTAMP column types to store timestamp values. The difference between the DATE and TIMESTAMP types is that the TIMESTAMP column type allows us to store fractional seconds while the DATE type... Read More The post How to map the Oracle TIMESTAMP WITH TIME ZONE with JPA appeared first on Vlad Mihalcea. ## One timezone for everything: k8tz and the Jakarta timestamp problem DevFeed: [One timezone for everything: k8tz and the Jakarta timestamp problem]() Original publisher: [Read original article]() Published: 2024-11-20T00:00:00Z Content type: article Language: en Sources: [Andika Ahmad Ramadhan -- Blog]() Topics: [Kubernetes admission controller](), [timezone](), [certificates](), [TLS (Transport Layer Security)](), [elasticsearch]() Tags: [certificates](), [elasticsearch](), [kubernetes-admission-controller](), [timezone](), [tls]() ### AI overview The article explains how k8tz applies Asia/Jakarta to Kubernetes pods through an admission controller, allowing public images such as Fluentd and Elasticsearch to use the platform timezone without image changes. It also describes three upstream patches for cert-manager support, certificate rotation without restarts, and configurable initContainer names. ### Source excerpt How we used k8tz to force Asia/Jakarta onto public images like Fluentd and Elasticsearch, and the three patches I sent upstream. ## PostgreSQL DevFeed: [PostgreSQL]() Original publisher: [Read original article]() Author: Derek Lee Published: 2022-03-01T00:00:00Z Content type: tutorial Language: en Sources: [art and science of coding]() Topics: [PostgreSQL](), [Databases](), [SQL](), [configuration](), [timezone](), [JSON]() Tags: [configuration](), [database](), [dev-recipes](), [installation](), [json](), [postgresql](), [psql](), [setup](), [sql](), [timezone](), [troubleshooting]() ### AI overview A reference guide to PostgreSQL installation, database and user management, SQL statements, configuration, time zone settings, psql commands, JSON fields, and troubleshooting connection problems. ### Source excerpt Installation / Setup ## Proposed Europe/Oslo timezone alias change could discard pre-1970 data and break Joda-Time behavior DevFeed: [Proposed Europe/Oslo timezone alias change could discard pre-1970 data and break Joda-Time behavior]() Original publisher: [Read original article]() Author: Stephen Colebourne (noreply@blogger.com) Published: 2021-09-25T00:55:00Z Content type: opinion Language: en Sources: [Stephen Colebourne]() Topics: [DateTime](), [Programming](), [systems](), [Operating system]() Tags: [blog](), [jdk](), [joda](), [operating-systems](), [smartphones](), [systems](), [timezone]() ### AI overview The article criticizes a proposed change to the IANA timezone database that would make Europe/Oslo an alias of Europe/Berlin because their post-1970 data matches. It argues that this could replace researched pre-1970 Oslo data with Berlin data and cause Joda-Time tests and timezone identifier handling to fail. ### Source excerpt The last time I wrote about the timezone database on this blog, the database was under threat from a lawsuit. Fortunately that lawsuit went away relatively quickly as the company involved got the message that their action was a big mistake. Unfortunately this time the mess is internal. Paul Eggert is the project lead of the timezone database hosted at IANA, a position referred to as the TZ Coordinator. He is an expert in the field, having been involved in documenting timezone data for decades. Unfortunately, he is currently ignoring all objections to an action only he seems intent on making to solve an invented problem that only he sees as important. The database is the world's principle source of timezone information. The data is included in everything from operating systems to smartphones to programming language development kits such as the JDK. While you may never have heard of it, the sheer pervasiveness of the data makes the potential impact of change or damage pretty huge. The timezone database contains information about how clocks have varies in each region around the world. The mandate of the project is to record this information from 1970 onwards. Of course, computers being what they are, a function that returns the timezone for a given date can be passed in a pre-1970 date as well as a post-1970 one. For this, and reasons of completeness, the timezone database contains pre-1970 data as well as post-1970 data. If you go to your JDK or operating system and ask for the timezone offset for 1920-01-01 for the ID "Europe/Oslo" or "Europe/Berlin" you will get an answer: DateTimeZone oslo = DateTimeZone.forID("Europe/Oslo"); System.out.println(oslo.getOffset(new DateTime(1948, 6, 1, 12, 0))); //prints 3600000 DateTimeZone berlin = DateTimeZone.forID("Europe/Berlin"); System.out.println(berlin.getOffset(new DateTime(1948, 6, 1, 12, 0))); //prints 7200000 The proposed change is to downgrade "Europe/Oslo" to be merely an alias for "Europe/Berlin". The rationale is th ## Handling Dates & Times in SQLite DevFeed: [Handling Dates & Times in SQLite]() Original publisher: [Read original article]() Published: 2020-09-04T16:35:01Z Content type: tutorial Language: en Sources: [Blogs on Ryan Harter]() Topics: [SQLite](), [Databases](), [DateTime](), [SQL](), [timezone](), [Kotlin]() Tags: [database](), [kotlin](), [sql](), [sqlite](), [time](), [timezone]() ### AI overview The article examines how to store dates and times in SQLite for a Kotlin app using Room. It explains that SQLite has no dedicated DateTime type and discusses problems with storing timestamps as Unix-epoch milliseconds, including timezone handling and query support. ### Source excerpt As I've been refactoring a fairly large section of Pigment, my coloring book app for adults, I came across some SQL code which I haven't touched in a very long time and didn't seem quite right. Part of Pigment's large library of coloring books and pages are the Daily books, which are a different book each month in which a new page is released each day. The day's page is free only for the day (for non-subscribers), and then reverts to being locked once the next page is released. Users can unlock a page forever by simply starting a coloring project with it while it's free, but there is a limited window in which it's available. ## Apache Airflow 1.10.10 DevFeed: [Apache Airflow 1.10.10]() Original publisher: [Read original article]() Author: Apache Airflow Published: 2020-04-09T00:00:00Z Content type: release Language: en Sources: [Apache Airflow Blog]() Topics: [airflow](), [Docker](), [Python](), [changelog](), [HashiCorp Vault](), [ui]() Tags: [3](), [airflow](), [apache-airflow](), [bug-fixes](), [changelog](), [docker](), [docker-image](), [dockerhub](), [environment-variables](), [hashicorp-vault](), [new-features](), [python](), [release](), [timezone](), [ui]() ### AI overview Apache Airflow 1.10.10 includes 199 commits since version 1.10.9, with 11 new features, 43 improvements, 44 bug fixes, and documentation changes. Notable additions include selectable RBAC UI timezones, production Docker images, secrets backends, DAG serialization for stateless webservers, and other UI and task-execution changes. ### Source excerpt Airflow 1.10.10 contains 199 commits since 1.10.9 and includes 11 new features, 43 improvements, 44 bug fixes, and several doc changes. Details: PyPI: https://pypi.org/project/apache-airflow/1.10.10/ Docs: https://airflow.apache.org/docs/1.10.10/ Changelog: http://airflow.apache.org/docs/1.10.10/changelog.html Some of the noteworthy new features (user-facing) are: Allow user to choose timezone to use in the RBAC UI Add Production Docker image support Allow Retrieving Airflow Connections & Variables from various Secrets backend Stateless Webserver using DAG Serialization Tasks with Dummy Operators are no longer sent to executor Allow passing DagRun conf when triggering dags via UI Allow user to choose timezone to use in the RBAC UI By default the Web UI will show times in UTC. It is possible to change the timezone shown by using the menu in the top right (click on the clock to activate it): Screenshot: Details: https://airflow.apache.org/docs/1.10.10/timezone.html#web-ui Note: This feature is only available for the RBAC UI (enabled using rbac=True in [webserver] section in your airflow.cfg). Add Production Docker image support There are brand-new production images (alpha quality) available for Airflow 1.10.10. You can pull them from the Apache Airflow Dockerhub repository and start using it. More information about using production images can be found in https://github.com/apache/airflow/blob/master/IMAGES.rst#using-the-images. Soon it will be updated with information how to use images using official helm chart. To pull the images you can run one of the following commands: docker pull apache/airflow:1.10.10-python2.7 docker pull apache/airflow:1.10.10-python3.5 docker pull apache/airflow:1.10.10-python3.6 docker pull apache/airflow:1.10.10-python3.7 docker pull apache/airflow:1.10.10 (uses Python 3.6) Allow Retrieving Airflow Connections & Variables from various Secrets backend From Airflow 1.10.10, users would be able to get Airflow Variables from Environment Variabl ## Labor, Bank Accounts, & CashDrawerShifts V2 APIs DevFeed: [Labor, Bank Accounts, & CashDrawerShifts V2 APIs]() Original publisher: [Read original article]() Author: Richard Moot Published: 2020-02-26T20:00:00Z Content type: release Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [API](), [releases](), [migration]() Tags: [apis](), [migration](), [migration-guide](), [new-features](), [releases](), [reporting](), [sorting](), [timezone](), [updates](), [webhooks]() ### AI overview Square announces updates to its Labor API, including V2 support for functionality previously provided by the V1 Timecards API, timezone recording, Labor Template objects, and V2 webhooks. It also releases V2 Bank Accounts and CashDrawerShifts APIs. ### Source excerpt Labor API updates -- Bank Accounts & CashDrawerShifts APIs released ## 2016: another year in review DevFeed: [2016: another year in review]() Original publisher: [Read original article]() Author: Monica Dinculescu Published: 2016-12-21T00:00:00Z Content type: article Language: en Sources: [Monica Dinculescu]() Topics: [GitHub](), [Instagram](), [Job](), [timezone]() Tags: [conferences](), [github](), [instagram](), [job](), [photos](), [timezone](), [year-in-review]() ### AI overview A personal 2016 year-in-review describing the author's GitHub projects and conference activity, Instagram and photography habits, frequent travel, language study, work, and other parts of their year. ### Source excerpt This year was pretty shit, so I wasn't very keen on doing one of these posts. So many of my favourite musicians died, so many of my favourite countries made mistakes, so many of my favourite people are worried and sad, and I am worried and sad with them. But this year was not the worst year we've ever had, or might ever have, so I will tell you the good parts of my year. Maybe you'll tell me the good parts of yours, and then for 3 minutes we will be less worried and sad, together. ❤ Here's life as GitHub saw it. Red text is dumb projects I've shipped (you can tell because the names don't make sense), black text is conferences I've spoken at: When I first looked at this graph I freaked out, because it looks like I did very little until April. Then someone reminded me that I have a job that isn't writing emoji apps, so I probably just you know, went to work and had normal evening hobbies like playing The Sims and hanging out with my cat. It just takes 4 months before I get antsy. Here's life as Instagram saw it. I've apparently started taking a lot more selfies, which is either pretty vain or slightly more self confident, or let's be honest, neither. This is also the first year when I took a lot of photos with my nice camera when traveling, but didn't have the energy to process or post any of them. Shit happens. 🛫✨🛬 I love traveling almost as much as I love cheese (which is a lot), and I'm so happy about all the places I got to go to this year. I travelled every month that didn't start with an A. I went to 17 cities and 8 countries. In July, I was at home for a total of 9 days. I am lucky that I work on a team that still tolerates the fact that every couple of months I'll just be in a different timezone, and I'm worried about when this will end and I'll have to stand still. My favourite trip was going to Taiwan, which was a country I didn't expect to love as much as I did. ✌🐼 I drank over 500 cups of coffee. I learnt about 60 traditional Chinese characters. I'm not ## How to Deal with Timezones the Active Support Way DevFeed: [How to Deal with Timezones the Active Support Way]() Original publisher: [Read original article]() Published: 2016-04-03T12:00:00Z Content type: article Language: en Sources: [Jake Yesbeck]() Topics: [Rails](), [Ruby](), [DateTime](), [Databases]() Tags: [database](), [how-to](), [rails](), [ruby](), [ruby-on-rails](), [time](), [timezone]() ### AI overview This tutorial explains how to handle timezones with Ruby on Rails' ActiveSupport. It covers supported timezone lists, parsing timestamps with Time.zone, safely applying temporary zones with Time.use_zone, and converting timestamps between zones, including displaying UTC database timestamps in a user's local time. ### Source excerpt "Well the code is bad because we had to..." is a phrase one might hear when discussing timezone offsets or daylight savings time considerations. Unless a developer is fortunate enough to work at a company whose userbase is entirely located in the UTC timezone, writing software aware of different timezones can be a daunting task. Luckily, Ruby on Rails' ActiveSupport library has some very nice built in features that can prove invaluable when facing time related issues. Built-in Timezones ActiveSupport in Ruby on Rails 4.0+ has a built in list of all supported timezones on the TimeZone class: ActiveSupport::TimeZone.all.map(&:name) #=> ["American Samoa", "International Date Line West", "Midway Island", "Hawaii", "Alaska", "Pacific Time (US & Canada)", "Tijuana", "Arizona", "Chihuahua", "Mazatlan", "Mountain Time (US & Canada)", "Central America", "Central Time (US & Canada)", "Guadalajara", ...] This list of timezones can be used when parsing strings into Time objects and converting an existing Time object from one timezone to another. For working with timezones in the United States, a handy us_zones method is also available on the same class. One interesting detail about this list of timezones is the lack of daylight savings time qualifiers. Keeping the timezones agnostic of daylight savings helps simplify their use. A developer does not need to worry about using one timezone object over another due to the time of the year. Time.use_zone The ActiveSupport library adds some functionality to built in Ruby classes. One of those additions is the ability to set and retrieve the zone attribute on the Time class. After a zone is set, it can be used when parsing strings into Time objects: Time.zone = 'Pacific Time (US & Canada)' Time.zone.parse('2016-04-01 10:00:00') #=> Fri, 01 Apr 2016 10:00:00 PDT -07:00 This code takes a timestamp string without a timezone specified and uses the value of Time.zone to correctly represent the time in the Pacific timezone. However, an immedia ## Nagios - downtime on host/service from command line with curl DevFeed: [Nagios - downtime on host/service from command line with curl]() Original publisher: [Read original article]() Author: Tom Published: 2016-01-11T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Deployment](), [Bash](), [cURL](), [Command-line interface](), [Script](), [Code](), [DateTime]() Tags: [bash](), [code](), [command-line](), [configuration](), [curl](), [deployment](), [downtime](), [http](), [linux](), [monitoring](), [script](), [timezone]() ### AI overview This tutorial presents a Bash script that uses curl to schedule downtime for a Nagios host or service during deployments or other heavy tasks. It explains parameters for targeting a service or an entire host, authentication, and adapting date formats for Nagios and timezone configurations. ### Source excerpt Sometimes deployment process or other heavy task may cause some Nagios checks to rise below normal levels and bother admin1. If this is expected and you want to add downtime on host/service during this task you may use this script: #!/bin/bash function die { echo $1; exit 1; } if [[ $# -eq 0 ]] ; then die "Give hostname and time in minutes as parameter!" fi if [[ $# -eq 1 ]] ; then MINUTES=15 else MINUTES=$2 fi HOST=$1 NAGURL=http://nagios.example.com/nagios/cgi-bin/cmd.cgi USER=nagiosuser PASS=nagiospassword SERVICENAME=someservice COMMENT="Deploying new code" export MINUTES echo "Scheduling downtime on $HOST for $MINUTES minutes..." # The following is urlencoded already STARTDATE=`date "+%d-%m-%Y %H:%M:%S"` # This gives us the date/time X minutes from now ENDDATE=`date "+%d-%m-%Y %H:%M:%S" -d "$MINUTES min"` curl --silent --show-error \ --data cmd_typ=56 \ --data cmd_mod=2 \ --data host=$HOST \ --data-urlencode "service=$SERVICENAME" \ --data-urlencode "com_data=$COMMENT" \ --data trigger=0 \ --data-urlencode "start_time=$STARTDATE" \ --data-urlencode "end_time=$ENDDATE" \ --data fixed=1 \ --data hours=2 \ --data minutes=0 \ --data btnSubmit=Commit \ --insecure \ $NAGURL -u "$USER:$PASS"| grep -q "Your command request was successfully submitted to Nagios for processing." || die "Failed to con tact nagios"; echo Scheduled downtime on nagios from $STARTDATE to $ENDDATE Threat this script as template with some tips: ## Active Support and Time DevFeed: [Active Support and Time]() Original publisher: [Read original article]() Published: 2015-08-30T12:00:00Z Content type: article Language: en Sources: [Jake Yesbeck]() Topics: [Ruby](), [Library](), [Programming](), [Software]() Tags: [article](), [developer](), [libraries](), [library](), [programming](), [ruby](), [timezone]() ### AI overview This article examines inconsistencies in Ruby's Active Support library when handling time. It covers convenient date and time calculations, timezone offsets, conversion to Epoch seconds with Ruby's Time#to_i, and the misleading assumption that every month has 30 days. ### Source excerpt If a list was compiled of useful Ruby libraries, Active Support would be close to the top. Based on the documentation alone, it is apparent that a very large amount of time went into thinking about the roles Active Support should play and the functionality it should support. From string manipulation to internationalization, Active Support seems to simply do it all. However, even a profoundly useful library like Active Support still has a few inconsistencies with everyone's favorite subject: Time Calculation. Time wounds all heals Personally, the thing that keeps me up at night, the monster in my closet, the beast waiting to grab my foot when I accidentally let it hang over the bed while sleeping, is time calculation in programming. Regardless of the task, however simple it may seem, calculating time offsets or time zone correction continues to be a tremendous pain point. Now, to demonstrate just how crazy things can be, let's pick on Active Support. Active Support grants a myriad of methods for even the most impatient Software Artisan. For example, if one were to ask for this instant in time, a day ago, Active Support makes it possible. 1.day.ago # => 2015-08-29 18:44:55 -0700 Likewise, basic date addition and subtraction is just as easy. three_days_from_now = Time.now + 3.days #=> 2015-09-01 18:46:34 -0700 three_days_from_now + 12.hours # => 2015-09-03 06:48:28 -0700 Great! Very simple, seemingly arbitrary time calculation has never been easier. So what could be the catch? Obviously there isn't one, if there were then this article would have to continue and I'm sure everyone has had quite enough. to_i is not always easy Had enough? Too bad. The topic of to_i still has to be discussed with relation to the Time class. Ruby's Time class exposes a method to_i which can be used to convert a Time to an Integer. This Integeris the sum of seconds passed since Epoch. Using Epoch time can be useful for some systems that want to avoid doing timezone conversion. In fact, it mi ## Postgres Datatypes - The ones you're not using. DevFeed: [Postgres Datatypes - The ones you're not using.]() Original publisher: [Read original article]() Author: Map Published: 2014-05-07T20:55:56Z Content type: article Language: en Sources: [Craig Kerstiens]() Topics: [Databases](), [timezone](), [DateTime](), [Gin](), [Extension]() Tags: [extension](), [gin](), [postgres](), [postgresql](), [timestamptz](), [timezone](), [uuid]() ### AI overview This article discusses less commonly used Postgres data types, including hstore, range types, timestamp with timezone, and UUIDs. It describes practical uses such as storing key-value data, constraining ranges, handling time zones, and supporting scalable identifiers. ### Source excerpt Postgres has a variety of datatypes, in fact quite a few more than most other databases. Most commonly applications take advantage of the standard ones - integers, text, numeric, etc. Almost every application needs these basic types, the rarer ones may be needed less frequently. And while not needed on every application when you do need them they can be an extremely handy. So without further ado let's look at some of these rarer but awesome types. hstore Yes, I've talked about this one before, yet still not enough people are using it. Of this list of datatypes this is one that could also have benefit for most if not all applications. Hstore is a key-value store directly within Postgres. This means you can easily add new keys and values (optionally), without haveing to run a migration to setup new columns. Further you can still get great performance by using Gin and GiST indexes with them, which automatically index all keys and values for hstore. It's of note that hstore is an extension and not enabled by default. If you want the ins and outs of getting hands on with it, give the article on Postgres Guide a read. Range types If there is ever a time where you have two columns in your database with one being a from, another being a to, you probably want to be using range types. Range types are just that a set of ranges. A super common use of them is when doing anything with calendaring. The place where they really become useful is in their ability to apply constraints on those ranges. This means you can make sure you don't have overlapping time issues, and don't have to rebuild heavy application logic to accomplish it. Timestamp with Timezone Timestamps are annoying, plain and simple. If you've re-invented handling different timezones within your application you've wasted plenty of time and likely done it wrong. If you're using plain timestamps within your application further there's a good chance they dont even mean what you think they mean. Timestamps with timezone o ## 4 Tips for Working with Dates in PostgreSQL DevFeed: [4 Tips for Working with Dates in PostgreSQL]() Original publisher: [Read original article]() Author: sensible.io team Published: 2013-08-26T11:47:00Z Content type: tutorial Language: en Sources: [Sensible]() Topics: [PostgreSQL](), [Rails]() Tags: [documentation](), [operator](), [postgresql](), [rails](), [time](), [timezone]() ### AI overview A tutorial on working with dates and times in PostgreSQL. It explains current-time functions such as now() and clock_timestamp(), time intervals and arithmetic, date-part extraction, and timezone-aware operations, with SQL examples. ### Source excerpt Those of us who come from Rails aren't surprised when we see something like 5.weeks.from_now or 3.days.ago + 2.hours, which makes working with dates much easier. But PostgreSQL got your back on this as well, you can just use the builtin functions and get most of the same functionality. Current Time/Date/Timestamp There are many ways of getting a current time, but first we need to distinguish between two types always returns current value (clock_timestamp()) always returns current value, unless in a transaction, in which case it returns the value from the beginning of the transaction (now()) Let's take a look at an example postgres=# BEGIN; postgres=# SELECT now(); now ------------------------------- 2013-08-26 12:17:43.182331+02 postgres=# SELECT now(); now ------------------------------- 2013-08-26 12:17:43.182331+02 postgres=# SELECT clock_timestamp(); clock_timestamp ------------------------------- 2013-08-26 12:17:50.698413+02 postgres=# SELECT clock_timestamp(); clock_timestamp ------------------------------- 2013-08-26 12:17:51.123905+02 As you can see, clock_timestamp() changes every time the statement is executed, but now() always returns the same value. It's also worth noting that both of these functions take timezone into account. Time interval, aka 3.days.ago You can easily create time intervals using the interval operator, for example interval '1 day' interval '5 days' interval '5 days' + interval '3 hours' interval '5 days 3 hours' As you can see, we can do simple math using the interval operator, which makes it very easy to construct things like 3.days.ago just by doing the following postgres=# SELECT now() - interval '3 days'; ?column? ------------------------------- 2013-08-23 12:23:40.069717+02 Extracting the day of the week and more Sometimes you just want to know the day of the week for a given date, or the century, or just the day. PostgreSQL has an extract() function which does just this. Just to put this into context the examples were executed ## A propos de Joda-Time DevFeed: [A propos de Joda-Time]() Original publisher: [Read original article]() Author: brice.dutheil@gmail.com (Brice Dutheil) Published: 2010-02-09T17:32:06Z Content type: tutorial Language: fr Sources: [The Coffee Workshop]() Topics: [Java](), [API](), [DateTime]() Tags: [api](), [bug](), [java](), [jdk](), [joda](), [thread](), [time](), [timezone]() ### AI overview This French developer article discusses the limitations of Java's legacy date and time API, including thread-safety, performance, and implementation issues. It introduces Joda-Time as a more consistent and usable alternative, explains its relationship to JSR-310, and demonstrates concepts such as immutable DateTime objects, instants, and time zones. ### Source excerpt Je suis un peu surpris de voir que beaucoup de développeurs utilisent encore énormément l'API temps du JDK. C'est la raison pour laquelle j'ajoute une nouvelle entrée sur le web à ce sujet.