Supabase is an open source Firebase alternative. Start your project with a Postgres database, Authentication, instant APIs, Edge Functions, Realtime subscriptions, and Storage.

Supabase

Hello, I have a question, everytime I edit a table in Supabase I usually get an error like these for example

Hello <@900453511211384834>!
This thread has been automatically created from your message in <#843999948717555735> a few seconds ago.

We have already mentioned the <@&951828363943759883> so that they can see your message and help you as soon as possible!

**Want to unsubscribe from this thread?**
Right-click the thread in Discord (or use the ``...`` menu) and select "Leave Thread" to unsubscribe from future updates.

**Want to change the title?**
Use the ``/title`` command!

**We have solved your problem?**
Click the button below to archive it.

I don't know if it's a Supabase problem but whevener I type
`(now at timezone 'America/New_York')` it gets sliced like that

I guess it's just a frontend problem but It got me worried

I don't know if you can put an expression like that in the front end

it's probably looking for an actual date string there

try using the query editor to put in that expression

For example you're putting a value into a bigint and the UI wants a numeric value and you're throwing "extval('listings_id..." in there, it's seeing it as a string so it's failing

Yeah but I didn't wrote the id one and Supabase allows me to write the expression in the timezone

The thing is that it's like cutting in half the string

Are you putting this in the "default value" field when creating the table or in the actual value for the table itself (as in, when doing data entry?)

Yes, default value field when creating/editing the table

And those are the suggestions of Supabase

Can you give the exact set of steps you're performing so I can give this to the front end team to investigate?  So for example, let me know exactly what you're clicking on and entering when you try to add the field.  If you could make a video that would be ideal, otherwise just give the steps and I'll try to duplicate it so the team can understand what's happening.  Thanks!

I think it's something weird with my current project, I'm trying to replicate it in an isolated environment but I wasn't able to do so, even tho the steps I normally do when creating a table are the following:

2. Add a new field called name, string with just a default value like 'cheese burger'
3. Rename the field `created_at` as `date_added` and add `(now at time zone 'America/New_York')` as default value
4. Uncheck the `Is Nullable` in `date_added`

It would look like this, then you click on the table and try to edit it, in this case I wasn't able to duplicate the error 😦

There was a bug-fix pushed to the front end yesterday that may have fixed your problem.

I saw it mentioned early this morning my time.