Differences

This shows you the differences between two versions of the page.

--- newdevs:code:import_csv_into_db [2023/02/27 13:26] – [Importing the Data] tlittle
+++ newdevs:code:import_csv_into_db [2023/02/27 13:28] – [Finessing the Data Prior to Import] tlittle
@@ Line 7: / Line 7: @@
 **Notes:**
   * If the table you're wanting to insert into uses an org, you'll want to edit your CSV file first to use the org IDs from Concerto.
-  * Don't include the column for ID from your production data--delete that.
+  * Don't include the column for ID from your production data.
   * If there are duplicate key constraints, check for those in your CSV *first* before you create your tables. For example, acq.provider has a duplicate key value unique constraint of "provider_name_once_per_owner". If you add a column in your CSV for dupe checking, you can use a formula to count how many times it appears and thus find dupes.
@@ Line 14: / Line 14: @@
 This assumes that Column A is the no-dupe column (name, in this case) and Column B is the org. So basically, count the number of times that the name in A2 appears with the same org that's in B2. Then if we fill that down the entire column, if you get anything above a 1 you have a dupe that you can filter for and remove.
+**TIP:** If you're not sure if your table includes a uniqueness constraint, here's a grep of Evergreen for the word "CONSTRAINT" which can point you toward where you might encounter a uniqueness constraint on the table you're working on: https://git.evergreen-ils.org/?p=Evergreen.git&a=search&h=HEAD&st=grep&s=CONSTRAINT
 ===== Importing the Data =====