 |
 |
 |
Module Reference |  |
 |
 |
|
|
|
Module Reference | |
|
|
The approach taken in the web.database module is to take the lowest common demoniator of features across databases and implement them in a way that provides consistent returns from the same SQL call across different databases.
The drawback of this approach is that some of the fields available in a particular database will not be available in the module. Also there is no support for complex SQL commands including indexes or views since not all databases support them. The approach is only to support what is available to all databases being used.
These drawbacks do not pose a significant problem because many projects will use the basic commands almost exclusively and will never need any of the features included in the SQL 92 specification but not supported by the modules.
If a database-specific feature is needed for a specific call you can always use SQL directly. By using the web.database module as much as possible you will still make your code more portable across databases should you ever need to change servers.
|
|
|
Module Reference | |
|
|