ProductReview Example: Difference between revisions
From DataFlex Wiki
Jump to navigationJump to search
mNo edit summary |
Hsymington (talk | contribs) m Changed from Web Programming to Web Applications category |
||
| (12 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
= Introduction = | |||
This page contains a description of an example project that can be used to study different implementation techniques using VDF as a backend. | |||
In this example the overall goal is to be able to see what users think about a particular item . As an added benefit - users can also share information about where to buy the particular items. | In this example the overall goal is to be able to see what users think about a particular item . As an added benefit - users can also share information about where to buy the particular items. | ||
| Line 11: | Line 11: | ||
*enter information about a known item | *enter information about a known item | ||
*supply information about the place where an item was bought. | *supply information about the place where an item was bought. | ||
*supply a | *supply a review of an item | ||
*Overview supplied | *Overview supplied reviews from other users | ||
The workspace is available here https://github.com/jacobandresen/ProductReview | |||
= [[DataDictionary|Data Dictionaries]] = | = [[DataDictionary|Data Dictionaries]] = | ||
We want to store information about users, places and known items. The other tables should hold sufficient information about the items and how the users liked them. | We want to store information about users, places and known items. The other tables should hold sufficient information about the items and how the users liked them. | ||
The following data dictionaries should now be available | The following data dictionaries should now be available (Note that attributes like "UserId" in Token implies a index on UserId on Token and a relation to the table "User") | ||
== | ==User== | ||
* | *UserId (Numeric) | ||
* | *LoginName (Ascii) | ||
*StreetAddress | *FirstName (Ascii) | ||
*City | *LastName (Ascii) | ||
*ZIPCode | *Password (Ascii) | ||
* | *EmailAddress (Ascii) | ||
*Rights (Ascii) | |||
*StreetAddress (Ascii) | |||
*City (Ascii) | |||
*ZIPCode (Ascii) | |||
*Country (Ascii) | |||
== | ==Token== | ||
* | *UserId (Numeric) | ||
* | *TokenValue (Ascii) | ||
*LastAccessed (Date) | |||
* | |||
==Shop== | ==Shop== | ||
* | *ShopId (Numeric) | ||
*Name | *Name (Ascii) | ||
*Type ( | *Type (Numeric) | ||
*Description | *Description (Ascii) | ||
* | *StreetAddress (Ascii) | ||
*City (Ascii) | |||
*ZIPCode (Ascii) | |||
*Country (Ascii) | |||
== | ==Product== | ||
* | *ProductId (Numeric) | ||
*Name | *Name (Ascii) | ||
*Type ( | *Type (Numeric) | ||
*Description | *Description (Ascii) | ||
* | *ShopId (Numeric) | ||
*Price | *Price (Numeric) | ||
==Review== | ==Review== | ||
* | *ReviewId (Numeric) | ||
* | *ItemId (Numeric) | ||
*Rating | *UserId (Numeric) | ||
*Comment | *Rating (Numeric) | ||
*Comment (Ascii) | |||
= Implementation = | = Implementation = | ||
| Line 62: | Line 69: | ||
[[ProductReview VDF AJAX implementation]] | [[ProductReview VDF AJAX implementation]] | ||
[[Category: Web | [[Category: Web Applications]] | ||
[[Category: Data Dictionaries]] | |||
Latest revision as of 14:14, 8 April 2020
Introduction
This page contains a description of an example project that can be used to study different implementation techniques using VDF as a backend.
In this example the overall goal is to be able to see what users think about a particular item . As an added benefit - users can also share information about where to buy the particular items.
To accomplish this, then users should be able to:
- login
- choose an item from a list
- enter information about a known item
- supply information about the place where an item was bought.
- supply a review of an item
- Overview supplied reviews from other users
The workspace is available here https://github.com/jacobandresen/ProductReview
Data Dictionaries
We want to store information about users, places and known items. The other tables should hold sufficient information about the items and how the users liked them.
The following data dictionaries should now be available (Note that attributes like "UserId" in Token implies a index on UserId on Token and a relation to the table "User")
User
- UserId (Numeric)
- LoginName (Ascii)
- FirstName (Ascii)
- LastName (Ascii)
- Password (Ascii)
- EmailAddress (Ascii)
- Rights (Ascii)
- StreetAddress (Ascii)
- City (Ascii)
- ZIPCode (Ascii)
- Country (Ascii)
Token
- UserId (Numeric)
- TokenValue (Ascii)
- LastAccessed (Date)
Shop
- ShopId (Numeric)
- Name (Ascii)
- Type (Numeric)
- Description (Ascii)
- StreetAddress (Ascii)
- City (Ascii)
- ZIPCode (Ascii)
- Country (Ascii)
Product
- ProductId (Numeric)
- Name (Ascii)
- Type (Numeric)
- Description (Ascii)
- ShopId (Numeric)
- Price (Numeric)
Review
- ReviewId (Numeric)
- ItemId (Numeric)
- UserId (Numeric)
- Rating (Numeric)
- Comment (Ascii)
