Difference between revisions of "Database description"
(→Hidden fields) |
(→Hidden fields) |
||
Line 42: | Line 42: | ||
**hash_password | **hash_password | ||
− | Example of unallowed | + | |
− | <sql>SELECT * FROM person; | + | Example of unallowed queries : |
+ | <sql>SELECT * FROM club; | ||
+ | |||
+ | SELECT hash_password FROM person; | ||
SELECT person.id, validity.* | SELECT person.id, validity.* | ||
FROM person | FROM person | ||
LEFT JOIN validity ON (person.id=validity.person_id);</sql> | LEFT JOIN validity ON (person.id=validity.person_id);</sql> |
Revision as of 17:38, 20 March 2015
Dump of OF 2.1 structure
Dump of OF 3.5 structure
booking table
The content of aircraft_id field in booking table might be null. In this case, it's an old booking made onto a non-existing aircraft or an aircraft which no longer exists; also called orphan booking.
Hidden fields
Following fields can not be exported and should not be in included in SELECT statement. Moreover, SELECT with wild-card * is not possible when there is one table including hidden fields:
- Table club:
- name
- info_cell
- logo
- logo_name
- logo_ext
- logo_size
- first_hour_displayed
- last_hour_displayed
- usual_profiles
- default_slot_range
- min_slot_range
- twilight_range
- mailing_list_name
- mailing_list_type
- default_timezone
- lang
- admin_num
- mail_from_address
- default_view_type
- address
- zipcode
- city
- state
- country
- phone
- fax
- default_notification
- welcome_cell
- Table parameter: all fields
- Table person:
- hash_password
Example of unallowed queries :
SELECT * FROM club; SELECT hash_password FROM person; SELECT person.id, validity.* FROM person LEFT JOIN validity ON (person.id=validity.person_id);