Hi villas, Yes I agree and did do that. My development is at point where my tables are defined. If I go much farther into development without deploying to the test server than it is too difficult to narrow down errors so i want to focus on the basic functionality up front. With all of the errors I have I really need to nail down the migration in small steps at a time.
To simplify my final design I'd really like to use the built in wiki. I'd also like to store my file objects in the database and not in the server. So my goal is to add a blob field to the auth.wiki(). So a small incremental approach is best for me while I fight through all of the challenges. Thanks, Bill On Monday, October 15, 2012 4:21:24 PM UTC-5, villas wrote: > > Hi Bill > > My experience is that it isn't a good idea to do experimental development > on a tricky DB. It is too easy to bite off more than you can chew. > > You will save heaps of time by prototyping your app on Sqlite first. Only > when your data schema becomes more stable should you move over to your DB. > > In this way you can more easily differentiate between your own coding > errors and any DB adaptor errors etc and this will make it quicker to learn > too. > > Just 2 cts, D > --
