People with teh Web design knowledge...

[Compudork]

..

 

[mugs]

The database contains a structure (the tables, indices, etc) and the data. If they already have the structure, they only need the data (such as if this database is from a popular product like the various free forum software that's out there).

I don't know what you mean by dynamic properties.

 

[nakedfrog]

It's data only. The rest of the stuff you're thinking of is in the code on the web server itself (if I'm understanding you correctly).

 

[Compudork]

..

 

[Compudork]

..

 

[SarcasticDwarf]

The database contains only data. The web code (PHP I would guess) is required to view and/or manipulate it, otherwise there is no real way for a regular visitor to access it.


*note, a database it dynamic in a way (auto increment and such), but not in the way you are suggesting.

 

[SarcasticDwarf]

Originally posted by: Compudork

Originally posted by: mugs
The database contains a structure (the tables, indices, etc) and the data. If they already have the structure, they only need the data (such as if this database is from a popular product like the various free forum software that's out there).

I don't know what you mean by dynamic properties.

Thanks, does this mean that if I pass them the SQL file, the structure is built into it, or they would have to re-create that structure themselves?

When you export the database structure, it should do it as a .sql file which will automatically tell the system how to rebuilt both the database and its data.

 

[kyzen]

They would have to re-create the structure themselves.

Think of the data as a bunch of Legos somebody just handed to you. Your website or application is the instruction manual to assemble those legos correctly in the way the picture on the box shows.

Yeah you could just give them the Legos and tell them to build the item on the box, but that might not turn out right.

 

[isasir]

A database will have the structure in the sense that it'll have many tables with links to various tables. What it won't have is a GUI/web-interface to it (PHP or whatever)

If I had an SQL database I could see all the data in there, but also get an idea of how the tables are all related, possibly giving me insight into a more efficient way to design my own database if I was planning on doing something similar.

 

[Compudork]

..

 

[thelanx]

Originally posted by: Compudork

Originally posted by: mugs
The database contains a structure (the tables, indices, etc) and the data. If they already have the structure, they only need the data (such as if this database is from a popular product like the various free forum software that's out there).

I don't know what you mean by dynamic properties.

Thanks, does this mean that if I pass them the SQL file, the structure is built into it, or they would have to re-create that structure themselves?

I'm not sure I understand you clearly, but if you export the database, the organization and structure of the database will be intact. However, the structure of the web end that manipulates and presents this data is separate.

Like Mugs I don't know what you mean by dynamic properties.

 

[isasir]

if you know SQL you could write script to the database directly instead of needing a GUI to do it for you.

If it was an Oracle database, for example, I think the statement, 'select table_name from user_tables;' would give me all the table names in the database and I could look at the structure for each one individually.

I could then type another SQL statement to insert data into a table.

You don't need an external source to use a database.

 

[Compudork]

..

 

[thelanx]

Originally posted by: Compudork
I really appreciate the responses, and thanks for keeping it simple.

Just so I can be a bit more informed for the future: If I'm looking at a SQL database, essentially, I would be able to tell there are various tables and dynamic elements, but they wouldn't actually occur without web code from an external source that I would need to create?

EDIT: damn I'm slow, you guys answered already!

A SQL database is a collection of tables and data. It doesn't require any web code to "occur" or exist. It is a stand alone system that is handled by the SQL software. However, often a SQL database is used to organize and serve data to a web application, such as an internet forum.

 

[DivideBYZero]

You have two major elements, the data and the Schema. The latter is a layout of the tables and their relationships It is often just a document; i.e., it is not held in the db in human readable form. This along with code/app documentation will allow a third party to access said data for their own ends.

The Web code components are essentially just retrieving data and manipulating it based upon what is returned/passed/stored by the database. Unless you use things like stored procedures a database is often relatively passive.

 

[Superwormy]

A database contains STRUCTURE *AND* DATA.

Anyone who says otherwise in this thread doesn't know jack sh!t about databases.

 

[torpid]

Originally posted by: Superwormy

A database contains STRUCTURE *AND* DATA.

Anyone who says otherwise in this thread doesn't know jack sh!t about databases.

Of course, the structure of any non system level data itself is often stored as data (system level data) in the database. That is why it is remarkably easy to interrogate schemas and manipulate them from modeling tools.

 

[GeekDrew]

Originally posted by: Superwormy

A database contains STRUCTURE *AND* DATA.

Anyone who says otherwise in this thread doesn't know jack sh!t about databases.

That's obvious, but I don't think that the OP was talking about that -- I think that he was confusing an SQL database with an application in PHP that uses an SQL database.