So, seems the tables are still there (along woith the data :) )... but web2py will not have anything to do them... Anybody have a trick to convince the server to look at them again? I don't see any other errors except that such and such a table (keyword) does not exist...
thanks again, Mart :) On Sep 12, 1:30 am, mart <[email protected]> wrote: > Hi, > > Not sure if this expected, or I basically committed a "no, no" when > doing web2py dev work, but... I wanted to have some child apps live > under a common parent app (seemed like a good idea at the time) and > all was working well. Then I decided that one child app needed to be > live a level (folder) higher to accommodate related forms. So I > created the folder structure I wanted, and when all was done, I > deleted the original controllers,models and views and re-launched the > parent app... and my wiki_tables disappeared! not the non-wiki_tables. > Is this expected behavior and more importantly, is there a way to get > them back? > > Maybe a "nice to have" would be a way to rename/move files with auto- > re-factoring right there from app-admin? > > Any help/ideas to get them back (if at all possible) would be great > and appreciated! It took a couple of weeks off and on to get the data > story straight, would hate to lose it (I know, should have backed > up... but didn't). > > This app was my first attempt at making the torturous Mercurial > experience somewhat bearable by using it as though it were something > like Perforce, easy and straight forward for basic tasks through a UI > (went with previous thread on web2py testing, source-control and but > tracking)... > > Thanks, > Mart :)
