Yaro: Are you saying that *.xls files can be imported to web2py?
On Mar 6, 11:20 am, Yarko Tymciurak <yark...@gmail.com> wrote: > Oh! I remember how this "bee" got in my hat: > > > > > > On Fri, Mar 6, 2009 at 9:08 AM, Yarko Tymciurak <yark...@gmail.com> wrote: > > On Fri, Mar 6, 2009 at 9:00 AM, mdipierro <mdipie...@cs.depaul.edu> wrote: > > >> the Makefile is only for building binaries. I do not expect users to > >> run the Makefile. > > >> I am against using a version control system that forces me to change > >> the code (put empty files in empty folders) because they cannot handle > >> empty folders. > > > Without agreeing or disagreeing - revision systems thru history did NOT > > track directories (there are interesting arguments all over this) - so > > strictly from a strength of logical position, this is weak - the > > counterpoint being "a system that fails when something null fails to exist > > (e.g. an empty directory) is not robust enough (other things could clean > > out empty directories). > > > Having said that - I think there is no stronger argument one way or the > > other - the strongest is: this is the way it is, and there is no reason at > > this point to change. > > > The robustness argument is general, and should enter into looking at > > anything new created: "how does this behave in some reasonable but > > exceptional condition?" > > Ah, yes -- yesterday, I spent "too much time" because fo excel's way of > generating csv's and this quite annoyed me. > > I tried to single step, and find where in web2py it was failing, and why - > my ONLY clue was the "failed to import data" flash, and the PARTIAL dataset > that managed to get in. I had 80 rows of 107 columns of data to inspect > that worked before 260 rows failed to make it in. I failed at single > stepping (I was looking at the wrong csv function at first!); I played with > changing the table definitions (simple first try: all default, make sure > the important field sizes are big enough). I pared down to a test data set > of just 3 rows which would fail on 2, succeed on one. In the end (with no > help from import csv messages). The last field was a comment, and in some > cases a multiple line comment (csv import handled this find). > > EVENTUALLY I found that _some_ rows with empty last fields only contained > 105 commas, whereas succeeding fields (and headers) contained 106 commas. > > Web2py messages were not hardly ANY help with this, so in this case - my > opinion (and experience) says that web2py did NOT operate sufficiently in an > exceptional condition (that is, did not give me enough information about the > failure - so discovering it took much effort). > > My final solution was to just export my big data set from the *.xls > spreadsheet - quite complicated and large, and generated by a dotNet > application - from Open Office, which at least generated a proper csv (I > think excel was exhibiting an off-by-one boundary error). > > Stay tuned on this one.... I will look if there is anything obvious that can > be done to improve the messages with csv imports (and important tool, as > it's turning out more and more as time goes on). > > Yarko > > > > > Enuff fun for a Friday. > > > It is how it is, and that's that! ;-) > > > Yarko > > >> Massimo > > >> On Mar 6, 8:23 am, BigBaaadBob <w...@rwwa.com> wrote: > >> > On Mar 5, 9:44 am, Yarko Tymciurak <yark...@gmail.com> wrote: > > >> > > The repository (git or otherwise - whoever maintains it) --- should > >> have a > >> > > placeholder to hold empty directories. > > >> > If the authoritative repository doesn't anchor these directories then > >> > you force other mirrors to be different to anchor these directories. > >> > I don't think that is a good approach. > > >> > I personally think a better approach is to either have web2py > >> > automatically create directories it needs or to have the Makefile do > >> > it.- Hide quoted text - > > - Show quoted text -- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
