Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.paradox    |    To crash or not to crash, asks Borland    |    9,834 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 9,310 of 9,834    |
|    Robert Molyneux to Dominick DiMantova    |
|    Re: Overview of Paradox database structu    |
|    31 Jul 08 13:26:06    |
      From: ibisnestremovespambit@iinet.net.au              Dominick DiMantova wrote:       > Hello, I would like to know if I can get an overview of a paradox database       > structure and architecture? I'm applying for a migration position that       requires       > familiarity with paradox database structure. Can someone help me by sending       > documentation to my email account, dominickdimantova@comcast.net? I really       > would appreciate this.       >       >       >       It is a file-based Relational Database Management System. That is, the       RDBMS tables and their various metadata and indices are held as lots of       files, rather than the single large file / all eggs in one basket of       Bill's boys pathetic offerings... (but I digress...)              You can use Paradox to inspect all tables and their fields, as well as       relational integrity constraints and meta-data.              Provided that your database has been properly designed, you will (a)       understand the wonderful nature of a properly designed RDBMS and (b)       question why you would want to migrate from it.              All business rules (unfortunately) are held in the application code       (Pascal look-alike called OPAL) and (obscure) table-driven components.              Thus, you may seek the long-gone and (deservedly) dead developers to       attempt to strangle them.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca