You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When uploading a CSV file of ~14k records, the table and columns are created, but the table is empty.
From the database tab, creating a new table with the "Add existing content to new table" button leads to the following messages flashing:
"Creating table X"
"Creating 42 columns..."
"Creating 14,525 rows..."
"An invalid response was received from the upstream server"
"Table X is good to go"
This leaves me at an impasse, since I know there are errors in my CSV file, but not sure what they are. Does anyone have any advice? Thanks!
A suggestion for Supabase: I'm loving supabase, enjoying building so quickly with it, and seeing how its progressing. Since you're prioritizing the broadening of the features atm, I'd find it helpful to have broad debugging and transparency features in place, like an error log. So in cases like CSV upload problems where the Supabase UI is exposing something complex in Postgres, there's a quick way to see what's going on and not lose momentum or have to switch back to standard Postgres tools.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When uploading a CSV file of ~14k records, the table and columns are created, but the table is empty.
From the database tab, creating a new table with the "Add existing content to new table" button leads to the following messages flashing:
"Creating table X"
"Creating 42 columns..."
"Creating 14,525 rows..."
"An invalid response was received from the upstream server"
"Table X is good to go"
This leaves me at an impasse, since I know there are errors in my CSV file, but not sure what they are. Does anyone have any advice? Thanks!
A suggestion for Supabase: I'm loving supabase, enjoying building so quickly with it, and seeing how its progressing. Since you're prioritizing the broadening of the features atm, I'd find it helpful to have broad debugging and transparency features in place, like an error log. So in cases like CSV upload problems where the Supabase UI is exposing something complex in Postgres, there's a quick way to see what's going on and not lose momentum or have to switch back to standard Postgres tools.
Beta Was this translation helpful? Give feedback.
All reactions