Hey everyone, love Xata - regrettably
Hey everyone, love Xata - regrettably didn't realize I had to opt in for the native Postgresql wire initially when creating a database so my long lived prod instance does not use the native wire and thus I am finding that replicating any of the data outside of Xata is a bit of a chore as postgres event handling is not an option for me. Does anyone have any good ideas, resources or a direction to point me to find a way to thoughtfully expose my data to external platforms without polling?
7 Replies
Hi there! Glad to hear you're enjoying Xata Lite.
To clarify, you have a database that is not postgres-enabled, is that correct? We actually changed this recently to remove the option; all newly created databases are now postgres-enabled.
In the long run, because we've deprecated non-postgres-enabled databases, you might be best served exporting your data and re-importing it into a new postgres-enabled database. Unfortunately, this may be a little tedious as you'll have to export/import the tables via
.csv files one at a time.
I'll ask the team to see if I can find any workaround.Ah ok good to know. Yea I had begun that process once before but the tedium got me - primarily the lack of native xata fields not working in the UI. Has that been resolved too?
Was also looking into extending/combining the xata agent application with xata_tools to create an automated AI assistance pipeline to help migrate
Unknown User•4mo ago
Message Not Public
Sign In & Join Server To View
@Gore for the linked fields there should be a dropdown to create a link when importing the
.csv file. You'll need to restore the tables in the correct order, one by one, with the parent tables first and tables with links second. I'm afraid there isn't a smarter way of doing it. The link fields will display as text at first in the import UI but if you click and scroll down you should see the option to set a link (see screenshot).
Yea I had begun that process once before but the tedium got me - primarily the lack of native xata fields not working in the UI. Has that been resolved too?@DigitalMischief could you clarify what you mean here? To the best of my knowledge, the xata fields should display correctly in postgres-enabled databases. Certain postgres types are not supported but should still display in the UI.
Unknown User•4mo ago
Message Not Public
Sign In & Join Server To View
In the docs there used to be explicit mention of certain fields not rendering proplerly in the UI if the database was postgres enabled