Skip to content

timetz columns exported as DateTime instead of PostgresTime — breaks INSERT and SELECT #7194

@mohamedhalim-maker

Description

@mohamedhalim-maker

Can we access your project?

  • I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

The exported row class incorrectly uses DateTime for timetz columns (e.g. getField('start_time'))

On write: supaSerialize sends a full ISO string "2026-06-08T19:00:00.000Z", which PostgreSQL rejects with:
PostgrestException: invalid input syntax for type time with time zone: "2026-06-08T19:00:00.000Z", code: 22007

On read: DateTime.tryParse("19:00:00+00") returns null, so all timetz fields are always null after fetching

Expected Behavior

On write: FlutterFlow should serialize timetz fields as a time-only string (e.g. "19:00:00+00"), which PostgreSQL accepts for timetz columns

On read: FlutterFlow should deserialize the time-only string returned by Supabase (e.g. "19:00:00+00") into a usable value

The exported row class should use getField / setField for timetz columns, using the existing PostgresTime class already present in [table.dart]— this is how it worked before

Steps to Reproduce

  1. Create a Supabase table with one or more columns of type timetz (time with time zone) — e.g. start_time, end_time
  2. Connect the table to FlutterFlow and export the project
  3. Attempt to INSERT a row using a FlutterFlow action that sets a timetz field via a DateTime value
  4. Observe the Postgres error in the console
  5. Alternatively, query the table and attempt to read the timetz field value in the app

Reproducible from Blank

  • The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4elMmAuYt1xMtJ7q6JbsExhmAsJn07UIIvlu5+FQwdJZetPYkLO+jxP2FoUtfiTAk7L2KJvGMx/vCOhYbuA+UnIRKYbaVx+s56egnKIWenb4ipDZC8Vn8nM9JJJVyA1Ka3mSRRJu51W10t2E+YDfORYAzUNqLSO2sdAPmYKZP/n3OqQ0SLb3kNh1JWeC/v

Visual documentation

Image

Environment

- FlutterFlow version:  v7.0.3
- Platform: windows
- Browser name and version: chrome 
- Operating system and version affected: web

Additional Information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: needs triageA potential issue that has not been confirmed as a bug.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions