Help coderanch get a
new server
by contributing to the fundraiser
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin

creating tables with rms best practices

Posts: 12
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
i'm trying to get a 'best practices' feeling for how to do database style tables with rms. say i want 2 tables: users and companies. rms doesn't support traditional database tables, so how to go about storing the data in a table like structure? as far as i can see, i've got two options:

a. create 2 recordStores. each recordStore is a table that will hold user and company info.

b. put everything into 1 recordStore and delimit the tables with a special character, such as ^.

my gut feeling is that creating separate recordStores for each table i need will make the project easier to understand and help keep the code clean, but am i going to get a performance hit from opening/maintaining so many recordStores? in the scenario above, i've only got 2 tables which means 2 recordStores, but this could easily grow to 20+ tables with a more complicated project.

anybody care to share their recommendations?

First, you drop a couch from the plane, THEN you surf it. Here, take this tiny ad with you:
We need your help - Coderanch server fundraiser
    Bookmark Topic Watch Topic
  • New Topic