Hi Simon, Yes, that looks like a CSV error message. Possibly, the CSV format is missing something expected... I would say that the problem occurs when converting from CSV. I would suggest that you take a look at Massimo's "CSVStudio" @ https://code.google.com/p/csvstudio/
i think it has something that will convert your CSV cols and rows to a model by generating "db.define_table(...) " Never the less, I will keep looking and see what turns up. I ran these on either a Linux flavour or MacOS... Unfortunately, I wasn't able to find a usable windows box today. I didn't run this against entire web2py filesets, I simply pointed to a location on my laptop, dumped different versions of dal.py there replacing them with what ever version I found - some old some more recent)... But they all worked. I hope this helps, Mart :) On Monday, January 7, 2013 4:05:40 PM UTC-8, Simon Ashley wrote: > > Thanks Mart, > > That's sort of fixed it, but starting to get additional issues with the > auth tables. > > > <https://lh4.googleusercontent.com/-HAmuqaTtnd0/UOtg3XU7NHI/AAAAAAAAAG8/LpeAt3Dm15w/s1600/copy+database2.png> > Think have seen this before with csv imports and have gotten around by > deleting suspect areas from the import source files. > (obviously not really an option here, and now wondering if that hack is > causing a postgres memory leak on import) > > ps. what OS and web2py version are you using? > (source 2.3.2 here) > --
