My experience with CSV import suggests that you need to delete the id column.
Also the lack of validation is a bit of a trap...once I edited an exported CSV with MS Excel, which silently reformatted all the dates to something like 1/2/2010. The edited file was 'successfully' imported into SQLite by web2py, but completely corrupted the table. Also if you happen to have any text that is non-UTF-8, (in my case a user supplied bibliographic information exported from MS Word), that can corrupt the table too. On Feb 16, 9:32 am, mdipierro <[email protected]> wrote: > On Feb 15, 2:05 pm, weheh <[email protected]> wrote: > > > During csv import via the admin interface, do I need to have all the > > fields from the db table present in the csv input file, or can I have > > just a few of the columns? > > as long as the other fields have default values or are not > "required=True" you can miss them. > > > Also, do validators get run during import? > > no. > > > I'm trying to import a csv file from a legacy database but it's not > > being read in and I'm not getting any error messages. How to debug > > this? > > Are you importing programmatic ally or vie the web interface? > > Does the file has a first row with column names? -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
