So I solved this issue but I want to explain it in detail because I believe it is a BUG and it took me all day to figure it out.
Basically, I created a “Date” column in my table and was expecting a date. It wasn’t working so I visited the baserow website (Date and time fields // Baserow) which showed me that US date fields are: MMDDYYY (note the three (3) Y’s). It looked as a typo but I gave it a try: I sent my date from another application to come to baserow as a date with format MMDDYYY. It was not working so to test further, I set the column as TEXT FIELD. Then, I was getting something, but it was gibberish. So after few minutes, I tried the ISO format which is YYYYMMDD and then boom I received a new row with the correct date, so I went and now changed the column to the “Date” type while forgetting to change/remove the previous row that had the MMDDYYY date. After I made this change, I could no longer view the table no matter what. I had to manually log-in to docker, and to postgresql, and remove that row, and as soon as I did that, I was able to view the table.
Nonetheless, we are very frustrated with baserow because we did not expect for the whole table to flip out so bad just because of a bad date. Why not receive an error? Maybe wipe it out for me? Maybe do not let me change the column or something. But it allowed me to proceed and in return broke the table.
Can we fix this for the future so that it never happens to anyone else?