Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import Text > Allow fields to be mapped more than once #32

Closed
sequelpro opened this issue Nov 9, 2013 · 5 comments
Closed

Import Text > Allow fields to be mapped more than once #32

sequelpro opened this issue Nov 9, 2013 · 5 comments
Assignees

Comments

@sequelpro
Copy link
Collaborator

Issue imported from Google Code: https://code.google.com/p/sequel-pro/issues/detail?id=32
Reporter:avenja...@gmail.com Date:2008-08-01 00:03:20 Status:Fixed Closed:2008-12-01

When importing a text file currently we are limited to mapping a column of data to a field in the
database once.

For example I have a data file with company details.
The database has both billing_company and shipping_company fields.
Should be able to map company field from data file to both fields in database.

Currently if a field has already been mapped you can't use it again.

@sequelpro
Copy link
Collaborator Author

Author:avenja...@gmail.com Date:2008-08-01 00:19:32

Sorry my bad. I should have double checked the interface first before posting this. You can ignore the above
comments

Ideally the field mapping sheet would show ALL the columns in the database and then allow you to pick the
columns from the data file to map to each database column.

This would then allow you to duplicate data across multiple fields as well as allow you to set a default for
fields where there is no corresponding field in the data file.

A combo box would probably work best in this scenario. pre-populated with the fields in the data file with
the option of setting a custom value.

Hope that makes more sense.

@sequelpro
Copy link
Collaborator Author

Author:abhibeck...@gmail.com Date:2008-08-01 00:31:06

OK, so to word it properly... :p

Instead of selecting the table column for each csv column, you want to select the csv column for each table
column. And as an aside, you think we should be able to set the value for table columns which will not be
mapped.

Sure, sounds great to me.

@sequelpro
Copy link
Collaborator Author

Author:avenja...@gmail.com Date:2008-08-01 00:37:41

Yup exactly right. The code for it is all in TableDump.m
I've had a quick play with it and got a combo box cell in there. Next is to swap the column data over and fix up a
few bugs. Will play with it more once I get back to Oz

@sequelpro
Copy link
Collaborator Author

Author:avenja...@gmail.com Date:2008-12-05 08:58:20

Fixed in r223 and r224.

Known Issue: A table must be selected in TABLES list first before using the Import... menu

@sequelpro
Copy link
Collaborator Author

Author:avenja...@gmail.com Date:2008-12-06 14:44:33

Known issue now fixed in r232

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant