|
|
|
|
|
|
|
Extra Alarm Fires Search Help & Guidelines
|
|
The following items give a general description of the extra alarm fires database, the fields you may search upon, and some example queries. These items should help you perform useful searches of the extra alarm data.
General Considerations: The search form for queries consists of these sections:
You are not allowed to select field three before you select field two. If you enter data into a field WITHOUT joining that field with another field, your entries will be disregarded. The operation selector contains an IS LIKE operator. It is probably the most 'powerfull' feature, and deserves some explanation. 'Is LIKE' is a text string searching operator. It can use 'wildcards' to search text. The wildcard is the % (percent) character. If you were looking for the text string 'John', and were searching by an 'equals' method, you would ONLY receive 'John' back as a response. 'John Smith' would NOT be found. However, if you searched for IS LIKE JOHN%, you are asking for any text string the STARTS WITH 'John', and has any text after the 'John'. Hence you results would find, 'John Smith', 'John Doe', and 'John Brown'. You WOULD NOT find 'Andrew John Black', however, because that text string does not BEGIN with 'John'. A new search for %John% (or %john%, not case sensitive) would find ALL instances of 'John' anywhere in the search. So... John% finds any text string STARTING with John. %John finds any text string ENDING with John. %John% finds any occurrence of the text string 'John'. The NULL Operator: The NULL or the NOT NULL operators are 'boolean', meaning they are either true or false. By 'true or false' it really means EMPTY or NOT EMPTY. A blank field will be FOUND if it is searched for as NULL. NOTE: - Special Considerations: The extra alarm fires data consists of a large amount of 'fires'. These 'fires' each consist of MULTIPLE records that define a particular fire. For example, a two alarm fire consists of (at least) TWO records (line entries), one for the 'first alarm' (and its responce), and another record for the second alarm (and its responce). Each of these records contain the master record data, such as the date, address, run number, etc. Each SET of a fires records (regardless of how many records a fire has) is identified in the database by a unique number (a primary key). Some of the fields you may search are contained in the 'master' record of a fire (example: the address), and some data is contained only in the subrecords of a fire (such as the companies responding). For example: A search for any fire that Engine 11 responed to will return ALL the records for that fire (regardless of the number of records). However a search for any fire the Engine 11 DID NOT respond to MAY produce unexpected results, in that the search will find ANY record that does not contain Engine 11, but the search will return ALL the records for the fire, some of which could contain Engine 11. Be aware. To assist in identifying which fields are which those fieldsd ONLY LOCATED IN SUBRECORDS are indicated in the following table by YELLOW highlighting. Those fields that belong to the 'master record' fields are not highlighted. Field Definitions:
Example searches: Single field searches: "Find all fires from 2000 through 2009" "Find all fires in 2003" "Find all fires of a third alarm or greater" "Find all fires that occurred in January" "Find all fires in the Fourth Battalion" "Find all fires that occurred in dwellings" "Find all fires associated with an explosion" Multi-field searches: "Find all fires in 1999 that Engine 11 responded to" "Find all fires in vacant commercial buildings" "Find all fires in occupied apartment buildings that required 10,000 or more gallons of water to extinguish" "Find all occupied commercial fires that required a HazMat responce" If these samples do not solve your query problems, you may send an email to, eatc7402@comcast.net and we will try to assist you in finding the data you desire. "Find all fires from 2000 to 2009"
Search results: SELECT * FROM extra_alarm_fires_addr WHERE fire_year LIKE ("20%") ORDER BY 'fire_year' DESC Your query returned 413 rows Your query returned 143 extra alarn fires Returned ALL fires from 2000 though 2009 BACK sample searches "Find all fires in 2003"
Search results: SELECT * FROM extra_alarm_fires_addr WHERE fire_year = ("2003") ORDER BY 'fire_year' DESC Your query returned 46 rows Your query returned 13 extra alarn fires Returned only the fires in 2003 BACK sample searches "Find all fires of a third alarm or greater"
SELECT * FROM extra_alarm_fires_addr WHERE max_alarms_numeric >= ("3.0") ORDER BY 'fire_year' DESC Your query returned 127 rows Your query returned 26 extra alarn fires Returned all fires equal to or greater than a third alarm BACK sample searches "I want to see just the records for Engine Companies"
SELECT * FROM extra_alarm_fires_addr WHERE fire_datefield LIKE ("%-01-%") ORDER BY 'fire_year' DESC Your query returned 50 rows Your query returned 18 extra alarn fires Returned all fires which occurred in January BACK sample searches "Find all fires in the Fourth Battalion"
SELECT * FROM extra_alarm_fires_addr WHERE box_or_location_id LIKE ("Box 4%") ORDER BY 'fire_year' DESC Your query returned 167 rows Your query returned 62 extra alarn fires Returned all fires with a Box number starting with a 4 (for the fourth battalion) BACK sample searches "Find all fires that occurred in dwellings"
SELECT * FROM extra_alarm_fires_addr WHERE occupancy_type LIKE ("%dwell%") ORDER BY 'fire_year' DESC Your query returned 126 rows Your query returned 51 extra alarn fires Returned all fires that occurred in dwellings BACK sample searches "Find all fires that are associated with an explosion"
SELECT * FROM extra_alarm_fires_addr WHERE fire_description LIKE ("%explos%") ORDER BY 'fire_year' DESC Your query returned 11 rows Your query returned 4 extra alarn fires Returns all fires with the phrase 'explos' in the fire description BACK sample searches "Find all fires in 1999 that Engine 11 responded to"
SELECT * FROM extra_alarm_fires_addr WHERE fire_year = ("1999") and engines LIKE ("%11%") ORDER BY 'fire_year' DESC Your query returned 34 rows Your query returned 12 extra alarn fires Returned all fires in 1999 that contain Engine 11 BACK sample searches "Find all fires in vacant commercial buildings"
SELECT * FROM extra_alarm_fires_addr WHERE vac_or_occupied LIKE ("%vac%") and occupancy_type LIKE ("%comm%") ORDER BY 'fire_year' DESC Your query returned 12 rows Your query returned 3 extra alarn fires Returned all fires in vacant commercial buildings BACK sample searches "Find all fires in occupied apartment buildings that required 10,000 or more gallons of water to extinguish"
SELECT * FROM extra_alarm_fires_addr WHERE vac_or_occupied LIKE ("%occ%") and occupancy_type LIKE ("%apart%") and water_used >= ("10000") ORDER BY 'fire_year' DESC Your query returned 13 rows Your query returned 4 extra alarn fires Returns all fires in occupied apartment buildings that required 10,000 or more gallons of water BACK sample searches "Find all occupied commercial fires that required a HazMat responce"
SELECT * FROM extra_alarm_fires_addr WHERE vac_or_occupied LIKE ("%occ%") and occupancy_type LIKE ("%comm%") and other LIKE ("%haz%") ORDER BY 'fire_year' DESC Your query returned 6 rows Your query returned 2 extra alarn fires Returns all occupied commercial fires that required a HazMat responce BACK sample searches |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Copyright © 2007, The Extra Alarm Association
of The Twin Cities, Inc. All Rights Reserved Last Edited: Thursday, April 05, 2007
-- [HOME] --
|