Post
by butte » Tue Jun 18, 2013 3:18 am
Never mind Yahoo, see PM.
This merely pursues a hunch.
It would be helpful to have the shop's URL for an initial look at products, etc.. It would also be helpful to have the first three rows, and at the very least the first row, of each supplier's .csv files (thus, formats); in, for example, one text file with a blank row (doubled hard returns) between the extracted first rows from the several source files. The latter single file would then likely be small enough to "attach" to PM. (Pasting the content into a usual post would probably make a complete mess of the format.)
Let's look at some basics. A database grid has a "magic" top row and left column, but is otherwise the same grid layout as a spreadsheet, which optionally may also be given "magic" top row and left column. The "magic" is definition in labeling, of row records, columnar fields. In .csv the rows are rows, the columns are between commas rather than between vertical bars. When file formats are interconverted, (1) every text comma in .csv or .sql enforces a vertical bar in spreadsheet or database grids, (2) every text row enforces a horizontal row. If the database and the .csv or spreadsheet files don't have the same numbers of columns or the same column labels, there's trouble waiting to happen.
The OC DATABASE has columns for fields, rows for records. The SUPPLIERS do not necessarily even have the same numbers or names of columns for the same fields among themselves, let alone matching OC.
That appears to be where your ongoing problem (among the several posts in your profile) in turn seems to originate and to continue. That accordingly seems also to frame the nature of what must be done to resolve it. Then the question is not whether that can be fully automated but instead whether you're up to the potential expense for setting it up. Solutions could well range from simple manual preparations to enforce .csv consistencies, all the way into a Java or C++ manipulation of .csv setups in order to force concordance among them, and removal of irrelevancies, prior to import into OC. Given the likely orders of magnitude (base ten) of suppliers, of shoes, of shoe options, and of changes among those per annum, a simpler approach might well be preferred over a more complex one.