Information générale
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Titre:
One table may be sufficient for an application
I’ve written an application of medium complexity which uniquely relies upon one table of simple structure (no Memo fields involved). The table (and the power of VFP) mimic all the tables and fields needed, with logical database normalization (master-detail), avoiding redundance as well. No Create/Alter Table will be necessary for adding new functionalities.
After one year of upgrade and real usage, pros and cons are clearer.
I want now to write and explain about the experimentation.
To begin with, I’m looking for articles over the Internet pertaining the idea of reducing the number of relational tables tipically used by applications.
A search through Google didn’t help.
So I’m asking for useful links about the topic.
Thanks.
Bruno Maddalozzo
MCP
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement