DB data

• Store different data types. You can specify the stored item as a string, a number, a phone (number), or a time (stamp). By specifying string, you can practically store any text into your database and have it sorted lexicographically. By using different data types the data will be sorted correctly and/or displayed uniformly for aesthetic purposes.
• Store image links and display images. You can specify DB items to be image links, and POD will intelligently replace the <img> tags in your html file with the image links stored in DB. This is best suitable for product catalogue, etc.
• Store email and www links. These work similar to image links, except that they will be automatically linked when displayed.
• Store a hit counting item on DB entries. You can specify an item to be a hit counting item and specify the initial value of the item when the DB entry is first added to the DB. When your customer or user viewed that entry, the hit counting item will be automatically incremented to reflect the interest in this entry. This is best suitable for tracking interest in your product catalogue, etc.
• Store multiple time stamp items in the DB. You can specify to let POD enter the time stamp for you using current system time, or enter the time stamp yourself. The time stamp is Y2K compliant and will be sorted intelligently. However, like many other software products, if the time stamp is earlier than 1/1/1970 or later than 2025, the sort function on such items may not work correctly even though the stamp will be stored and displayed correctly.
• Time stamp can be displayed and/or input in 10 different format.
• Convert items even after your DB is created. You can let POD to change the names, sizes, or order of the items in the database, and POD will correctly transform your DB to new DB schema (as a precaution, please back up your DB first before you convert just in case unforseen event happens during conversion).
• Specify which items in an entry are required to be non-empty for the entry to be considered valid. This way you can avoid getting empty entries into the DB that do not make sense.
• Specify the size of the items in your database entries. The sizes can be later changed as described above.