Resolving RQData Timezone Errors with the Database Timezone

Summary

This brief forum exchange addresses timezone errors when requesting data through RQData. The suggested fix is to attach VeighNa’s database timezone to the start datetime, so the requested time is timezone-aware. The original poster confirms that applying this change resolved the problem.

The example concerns the start value; the question also mentions an end value, but the exchange does not show how to set it. It gives no details about the exact error, the database timezone configuration, or whether the same fix applies across all installations and date ranges. Treat it as a narrow troubleshooting tip for aligning request datetimes with VeighNa’s database timezone, rather than a general guide to timezone handling.

Key ideas

• RQData requests may fail when their datetime values lack timezone information.
• The reply recommends using VeighNa’s database timezone for the request start datetime.
• The poster reports that the change solved their issue.
• The exchange does not document an equivalent end datetime example or broader timezone behavior.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.