Technical References - Database format

numero = 214
interpreted = N
texte = WebDNA can open any number of databases, each of which can have its own field structure. The number of records is only limited by the amount of RAM given to WebDNA (when used as a plugin, you must give more RAM to the web server software itself). In case the number of open databases grows larger than the available RAM, then WebDNA will just close unused databased to make room.

WebDNA recognizes Tab-Delimited text files, Microsoft Access and FileMaker Pro's "Merge" Quote-Comma-Delimited format, and any ODBC-compliant SQL database.

Tab-Delimited Format: the following is an example of a database with custom fields. It was created in FileMaker Pro and exported using the "Tab-Delimited" format.

Contents of Tab-Delimited format AddressList.db file (the .db file extension is a convention only: it is not required):

------------------------------------------------------------------name     address                       city          state   zipGrant    1180 Central Ave              San Marcos    CA      92079PCS      11770 Bernardo Plaza Court    San Diego     CA      92128------------------------------------------------------------------

Notice that the fields are separate by tabs

Merge Format: the following is an example of a database that has been exported to Merge format from a FileMaker Pro or Access database. Notice that FileMaker automatically puts the field names across the top of the file, so you do not have to make any changes after exporting.

Contents of Merge format AddressList.db file (the .db file extension is a convention only: it is not required):

----------------------------------------------------------------name,address,city,state,zip"Grant","1180 Central Ave","San Marcos","CA","92079""PCS","11770 Bernardo Plaza Court","San Diego","CA","92128"----------------------------------------------------------------

WebDNA always saves databases in tab-delimited format, regardless of what they originally were. Any Delete, Append, or Replace action causes a database to be written to disk in tab-delimited format (except when using SQL, which has its own format).

New ".hdr" file specification: if the database you wish to import does not already contain a list of fieldnames in the first row, then you can create a second file called "xxx.hdr" that contains just the fieldnames, and WebDNA will automatically use those fieldnames. If the database is in Merge format, then the .hdr file must also be in Merge format. Example Tab-delimited database that uses a header file:
----- Products.tab ---------------------------------------------Grant    1180 Central Ave                San Marcos   CA   92079PCS      11770 Bernardo Plaza Court      San Diego    CA   92128--------------------------------------------------------------------- Products.hdr ---------------------------------------------name     address                         city        state   zip----------------------------------------------------------------
Example Merge-format database that uses a header file:
----- Products.merge -------------------------------------------"Grant","1180 Central Ave","San Marcos","CA","92079""PCS","11770 Bernardo Plaza Court","San Diego","CA","92128"--------------------------------------------------------------------- Products.hdr ---------------------------------------------name,address,city,state,zip----------------------------------------------------------------

Potential non alphanumeric characters inside a database should always be recorded using [url]...[/url] to assure proper formatting and interpretation.

WebDNA can open any number of databases, each of which can have its own field structure. The number of records is only limited by the amount of RAM given to WebDNA (when used as a plugin, you must give more RAM to the web server software itself). In case the number of open databases grows larger than the available RAM, then WebDNA will just close unused databased to make room.

WebDNA recognizes Tab-Delimited text files, Microsoft Access and FileMaker Pro's "Merge" Quote-Comma-Delimited format, and any ODBC-compliant SQL database.


Tab-Delimited Format:
the following is an example of a database with custom fields. It was created in FileMaker Pro and exported using the "Tab-Delimited" format.

Contents of Tab-Delimited format AddressList.db file (the .db file extension is a convention only: it is not required):


------------------------------------------------------------------
name address city state zip
Grant 1180 Central Ave San Marcos CA 92079
PCS 11770 Bernardo Plaza Court San Diego CA 92128
------------------------------------------------------------------

Notice that the fields are separate by tabs


Merge Format: the following is an example of a database that has been exported to Merge format from a FileMaker Pro or Access database. Notice that FileMaker automatically puts the field names across the top of the file, so you do not have to make any changes after exporting.


Contents of Merge format AddressList.db file (the .db file extension is a convention only: it is not required):


----------------------------------------------------------------
name,address,city,state,zip
"Grant","1180 Central Ave","San Marcos","CA","92079"
"PCS","11770 Bernardo Plaza Court","San Diego","CA","92128"
----------------------------------------------------------------

WebDNA always saves databases in tab-delimited format, regardless of what they originally were. Any Delete, Append, or Replace action causes a database to be written to disk in tab-delimited format (except when using SQL, which has its own format).



New ".hdr" file specification:
if the database you wish to import does not already contain a list of fieldnames in the first row, then you can create a second file called "xxx.hdr" that contains just the fieldnames, and WebDNA will automatically use those fieldnames. If the database is in Merge format, then the .hdr file must also be in Merge format.
Example Tab-delimited database that uses a header file:
----- Products.tab ---------------------------------------------
Grant 1180 Central Ave San Marcos CA 92079
PCS 11770 Bernardo Plaza Court San Diego CA 92128
----------------------------------------------------------------

----- Products.hdr ---------------------------------------------
name address city state zip
----------------------------------------------------------------


Example Merge-format database that uses a header file:
----- Products.merge -------------------------------------------
"Grant","1180 Central Ave","San Marcos","CA","92079"
"PCS","11770 Bernardo Plaza Court","San Diego","CA","92128"
----------------------------------------------------------------

----- Products.hdr ---------------------------------------------
name,address,city,state,zip
----------------------------------------------------------------

Potential non alphanumeric characters inside a database should always be recorded using [url]...[/url] to assure proper formatting and interpretation.


DOWNLOAD WEBDNA NOW!

Top Articles:

Tips and Tricks

A list of user-submitted tips ...

AWS Raw WebDNA LAMP-Plus WebServer

Amazon Web Services (AWS) README for Machine Image ID...

Technical Change History

This Technical Change History provides a reverse chronological list of WebDNA changes...

WebDNA Modules

A list of the currently available modules...

F.A.Q

A compilation of some user's questions...

Download WebDNA Applications

WebDNA applications...

Related Readings:

[hideif]

[HideIf Comparison]Hide This HTML[/HideIf]...

[addlineitem]

Adds a product to the specified shopping cart...

[capitalize]

Capitalizes the first letter of all words in a sentence...

[switch]

Executes the WebDNA inside the only [case] context which matches the given value...

[writefile]

[writefile] functions allows you to perform a wide variety of tasks...

[setheader]

Changes header values in a shopping cart...