Re: Comments in SQL?


"Steve" <no.one@xxxxxxxxxxx> wrote in message
news:M6R4h.115$MX1.87@xxxxxxxxxxxxxxx
| I had a thought, which can be dangerous, haha. Is is possible to store
each
| table definition in it's own file, and then simply have one file that
| references all of the others? Like includes in other languages? If this
is
| possible, it would have many advantages for me and my website. Anyone?

look...is there *any* reason anyone would care about your db setup files
but
you or an administrator? do not comment a bunch of crap in your db setup
files. you should have actual DOCUMENTATION that lays out the table design
of every table and also describes the relationships they possibly have to
one another. further, you should have that documentation describe the
overall strategy of the purpose of what you're storing and how your
structure supports that end. anything else is less than adequate...and
trying to do ANY of this directly in your db setup is utterly a misgiving.
that is, unless this site is solely for your own amusement.

hth,

me


Thanks for the input, and although it is well received, I must point out
that the website I'm building is meant to be polymorphic, and it is being
designed to grow in unforseen directions. In order to accomodate this
growth, there does needs to be solid documentation, so as to cut down on
design errors, which there will also undoubtably be, and also to promote
understanding of what the table is, and what its reason for being is. The
reason for the seperation of the files is so that people can edit/add the
tables needed for the websites expansion and improvement, without having to
sort through or understand all of the tables of the website. Knowing this,
do you still think its a mistake to put the comments in the database
definition files? I really want your opinion. The database aspects are
giving me more troubles than anything else. It just seems so foreign to me
still, and I expect that a guru could easily find more than one problem with
my databases structure. Anyhow, I appreciate the advice, and I'm eager for
more.

Thanks,

sTony.



.

Relevant Pages

  • Re: Missing something obvious?
    ... "David Portas" wrote... ... websites, a page would belong to a section, a section to a website. ... I have since starting changing the database design so that these ...
    (microsoft.public.sqlserver.programming)
  • Re: Comments in SQL?
    ... design errors, which there will also undoubtably be, and also to promote ... sort through or understand all of the tables of the website. ... The database aspects are ... The gain you get without comments are smaller source files. ...
    (alt.php)
  • Re: Website Excel Spreadsheet for Non-Excel Users
    ... This will allow you too put together the basic structure of a website, although if its for a company and you want too keep a reputation and online presence I would really push you too get a professionaly designed website and tell them about the ordering system idea. ... Start with some HTML tutorials, you may find it easier to work with Tables too start with, although I would highly recommend you to learn XHTML & CSS coding, this is the best way too design a website too the latest of Standards. ... For you ordering system, you will need to learn the basics of setting up an ODBC connection on your home pc that will allow you to remotely connect to an online database. ...
    (microsoft.public.inetsdk.html_authoring)
  • Sr. Java Developer
    ... Equipment or software design, engineering and/or development for ... Participation in the development and preparation of documentation for, ... maintains databases, ... Experience with Object Oriented Techniques ...
    (comp.lang.java.programmer)
  • Re: Using the same template for each page
    ... >I'm making a website where each page has the same design, ... >a bad idea to put the same code/html in each page so what is the best ... content records in a database. ... Unless the directory structure is essential to your design, ...
    (comp.lang.php)