![]() ![]() I attached a quick sketch mockup (sorry if's a little rough) of something that maybe could utilize that white space at the bottom. Though, the way you handled import I think you could tweak that slightly for CREATE. Installing Postgres.app Download Move to Applications folder Double Click If you don't move Postgres.app to the Applications folder, you will see a warning about an unidentified developer and won't be able to open it. Or you're just compiling datasets in a folder and this way you can group them at once.ĬREATE TABLE from import would be really convenient, but it needs a more complex UI, so we've decided to focus on importing into existing tables for nowĪgreed, this might be a bit of an undertaking as you would likely have to come up with a nice interface for picking data types as well as potential automated guessing. Sure, like you mentioned the use case is sometimes CSVs are too big to work or for whatever reason split up into multiple files but retain the same structure (all have headers, all have the same columns). That way at least some of the work is done if not all.Ĭould you explain your use case for selecting multiple CSV files for import? Do you have data split up into multiple files? Or do you want to import data for multiple tables at once? Third, using a cloud solution like Skyvia which gets the CSV file from an online location like an FTP source or a cloud storage like Google Drive. Second, using the pgAdmin tool’s import/export. ![]() Column name matching is something we want to add and we've already experimented with, but we're not sure yet how to handle the case when only some column names match.Ī potential solution that might work, is after you've found matching columns is to loop through the remaining columns that don't. You have 3 options to import CSV files to PostgreSQL: First, using the COPY command through the command line.
0 Comments
Leave a Reply. |