gem_id stringlengths 20 25 | id stringlengths 24 24 | title stringlengths 3 59 | context stringlengths 151 3.71k | question stringlengths 1 270 | target stringlengths 1 270 | references list | answers dict |
|---|---|---|---|---|---|---|---|
gem-squad_v2-train-7500 | 5a8c424cfd22b3001a8d8664 | Database | For instance, a common use of a database system is to track information about users, their name, login information, various addresses and phone numbers. In the navigational approach all of this data would be placed in a single record, and unused items would simply not be placed in the database. In the relational approach, the data would be normalized into a user table, an address table and a phone number table (for instance). Records would be created in these optional tables only if the address or phone numbers were actually provided. | How is information discarded in a navigational system? | How is information discarded in a navigational system? | [
"How is information discarded in a navigational system?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7501 | 5a8c424cfd22b3001a8d8665 | Database | For instance, a common use of a database system is to track information about users, their name, login information, various addresses and phone numbers. In the navigational approach all of this data would be placed in a single record, and unused items would simply not be placed in the database. In the relational approach, the data would be normalized into a user table, an address table and a phone number table (for instance). Records would be created in these optional tables only if the address or phone numbers were actually provided. | What happens to full data fields in a navigational system? | What happens to full data fields in a navigational system? | [
"What happens to full data fields in a navigational system?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7502 | 5a8c424cfd22b3001a8d8666 | Database | For instance, a common use of a database system is to track information about users, their name, login information, various addresses and phone numbers. In the navigational approach all of this data would be placed in a single record, and unused items would simply not be placed in the database. In the relational approach, the data would be normalized into a user table, an address table and a phone number table (for instance). Records would be created in these optional tables only if the address or phone numbers were actually provided. | How is information lost in a relational system? | How is information lost in a relational system? | [
"How is information lost in a relational system?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7503 | 572f703ca23a5019007fc629 | Database | Linking the information back together is the key to this system. In the relational model, some bit of information was used as a "key", uniquely defining a particular record. When information was being collected about a user, information stored in the optional tables would be found by searching for this key. For instance, if the login name of a user is unique, addresses and phone numbers for that user would be recorded with the login name as its key. This simple "re-linking" of related data back into a single collection is something that traditional computer languages are not designed for. | How is information accessed in a relational model? | How is information accessed in a relational model? | [
"How is information accessed in a relational model?"
] | {
"text": [
"a \"key\""
],
"answer_start": [
126
]
} |
gem-squad_v2-train-7504 | 572f703ca23a5019007fc62a | Database | Linking the information back together is the key to this system. In the relational model, some bit of information was used as a "key", uniquely defining a particular record. When information was being collected about a user, information stored in the optional tables would be found by searching for this key. For instance, if the login name of a user is unique, addresses and phone numbers for that user would be recorded with the login name as its key. This simple "re-linking" of related data back into a single collection is something that traditional computer languages are not designed for. | What is a key used for? | What is a key used for? | [
"What is a key used for?"
] | {
"text": [
"uniquely defining a particular record"
],
"answer_start": [
135
]
} |
gem-squad_v2-train-7505 | 572f703ca23a5019007fc62b | Database | Linking the information back together is the key to this system. In the relational model, some bit of information was used as a "key", uniquely defining a particular record. When information was being collected about a user, information stored in the optional tables would be found by searching for this key. For instance, if the login name of a user is unique, addresses and phone numbers for that user would be recorded with the login name as its key. This simple "re-linking" of related data back into a single collection is something that traditional computer languages are not designed for. | What technique is used to collect into one place? | What technique is used to collect into one place? | [
"What technique is used to collect into one place?"
] | {
"text": [
"re-linking"
],
"answer_start": [
467
]
} |
gem-squad_v2-train-7506 | 572f703ca23a5019007fc62c | Database | Linking the information back together is the key to this system. In the relational model, some bit of information was used as a "key", uniquely defining a particular record. When information was being collected about a user, information stored in the optional tables would be found by searching for this key. For instance, if the login name of a user is unique, addresses and phone numbers for that user would be recorded with the login name as its key. This simple "re-linking" of related data back into a single collection is something that traditional computer languages are not designed for. | How is data in an optional table accessed? | How is data in an optional table accessed? | [
"How is data in an optional table accessed?"
] | {
"text": [
"by searching for this key"
],
"answer_start": [
282
]
} |
gem-squad_v2-train-7507 | 5a8c42cdfd22b3001a8d866b | Database | Linking the information back together is the key to this system. In the relational model, some bit of information was used as a "key", uniquely defining a particular record. When information was being collected about a user, information stored in the optional tables would be found by searching for this key. For instance, if the login name of a user is unique, addresses and phone numbers for that user would be recorded with the login name as its key. This simple "re-linking" of related data back into a single collection is something that traditional computer languages are not designed for. | How is information hidden in a relational model? | How is information hidden in a relational model? | [
"How is information hidden in a relational model?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7508 | 5a8c42cdfd22b3001a8d866c | Database | Linking the information back together is the key to this system. In the relational model, some bit of information was used as a "key", uniquely defining a particular record. When information was being collected about a user, information stored in the optional tables would be found by searching for this key. For instance, if the login name of a user is unique, addresses and phone numbers for that user would be recorded with the login name as its key. This simple "re-linking" of related data back into a single collection is something that traditional computer languages are not designed for. | What is a key no longer used for? | What is a key no longer used for? | [
"What is a key no longer used for?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7509 | 5a8c42cdfd22b3001a8d866d | Database | Linking the information back together is the key to this system. In the relational model, some bit of information was used as a "key", uniquely defining a particular record. When information was being collected about a user, information stored in the optional tables would be found by searching for this key. For instance, if the login name of a user is unique, addresses and phone numbers for that user would be recorded with the login name as its key. This simple "re-linking" of related data back into a single collection is something that traditional computer languages are not designed for. | What technique is used to collect into nowhere? | What technique is used to collect into nowhere? | [
"What technique is used to collect into nowhere?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7510 | 5a8c42cdfd22b3001a8d866e | Database | Linking the information back together is the key to this system. In the relational model, some bit of information was used as a "key", uniquely defining a particular record. When information was being collected about a user, information stored in the optional tables would be found by searching for this key. For instance, if the login name of a user is unique, addresses and phone numbers for that user would be recorded with the login name as its key. This simple "re-linking" of related data back into a single collection is something that traditional computer languages are not designed for. | How is data in an optional table removed? | How is data in an optional table removed? | [
"How is data in an optional table removed?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7511 | 572f7193947a6a140053c970 | Database | Just as the navigational approach would require programs to loop in order to collect records, the relational approach would require loops to collect information about any one record. Codd's solution to the necessary looping was a set-oriented language, a suggestion that would later spawn the ubiquitous SQL. Using a branch of mathematics known as tuple calculus, he demonstrated that such a system could support all the operations of normal databases (inserting, updating etc.) as well as providing a simple system for finding and returning sets of data in a single operation. | How does a program collect information using a navigational system? | How does a program collect information using a navigational system? | [
"How does a program collect information using a navigational system?"
] | {
"text": [
"require programs to loop"
],
"answer_start": [
40
]
} |
gem-squad_v2-train-7512 | 572f7193947a6a140053c971 | Database | Just as the navigational approach would require programs to loop in order to collect records, the relational approach would require loops to collect information about any one record. Codd's solution to the necessary looping was a set-oriented language, a suggestion that would later spawn the ubiquitous SQL. Using a branch of mathematics known as tuple calculus, he demonstrated that such a system could support all the operations of normal databases (inserting, updating etc.) as well as providing a simple system for finding and returning sets of data in a single operation. | What is used to solve the problem of looping? | What is used to solve the problem of looping? | [
"What is used to solve the problem of looping?"
] | {
"text": [
"a set-oriented language"
],
"answer_start": [
228
]
} |
gem-squad_v2-train-7513 | 572f7193947a6a140053c972 | Database | Just as the navigational approach would require programs to loop in order to collect records, the relational approach would require loops to collect information about any one record. Codd's solution to the necessary looping was a set-oriented language, a suggestion that would later spawn the ubiquitous SQL. Using a branch of mathematics known as tuple calculus, he demonstrated that such a system could support all the operations of normal databases (inserting, updating etc.) as well as providing a simple system for finding and returning sets of data in a single operation. | What computer language came about as a result of the looping problem? | What computer language came about as a result of the looping problem? | [
"What computer language came about as a result of the looping problem?"
] | {
"text": [
"SQL"
],
"answer_start": [
304
]
} |
gem-squad_v2-train-7514 | 572f7193947a6a140053c973 | Database | Just as the navigational approach would require programs to loop in order to collect records, the relational approach would require loops to collect information about any one record. Codd's solution to the necessary looping was a set-oriented language, a suggestion that would later spawn the ubiquitous SQL. Using a branch of mathematics known as tuple calculus, he demonstrated that such a system could support all the operations of normal databases (inserting, updating etc.) as well as providing a simple system for finding and returning sets of data in a single operation. | What type of math was used to create a system to find data sets? | What type of math was used to create a system to find data sets? | [
"What type of math was used to create a system to find data sets?"
] | {
"text": [
"tuple calculus"
],
"answer_start": [
348
]
} |
gem-squad_v2-train-7515 | 572f7193947a6a140053c974 | Database | Just as the navigational approach would require programs to loop in order to collect records, the relational approach would require loops to collect information about any one record. Codd's solution to the necessary looping was a set-oriented language, a suggestion that would later spawn the ubiquitous SQL. Using a branch of mathematics known as tuple calculus, he demonstrated that such a system could support all the operations of normal databases (inserting, updating etc.) as well as providing a simple system for finding and returning sets of data in a single operation. | Who used tuple calculus to show the functionality of databases? | Who used tuple calculus to show the functionality of databases? | [
"Who used tuple calculus to show the functionality of databases?"
] | {
"text": [
"Codd"
],
"answer_start": [
183
]
} |
gem-squad_v2-train-7516 | 5a8c4347fd22b3001a8d8673 | Database | Just as the navigational approach would require programs to loop in order to collect records, the relational approach would require loops to collect information about any one record. Codd's solution to the necessary looping was a set-oriented language, a suggestion that would later spawn the ubiquitous SQL. Using a branch of mathematics known as tuple calculus, he demonstrated that such a system could support all the operations of normal databases (inserting, updating etc.) as well as providing a simple system for finding and returning sets of data in a single operation. | How does a program collect information using a normalized system? | How does a program collect information using a normalized system? | [
"How does a program collect information using a normalized system?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7517 | 5a8c4347fd22b3001a8d8674 | Database | Just as the navigational approach would require programs to loop in order to collect records, the relational approach would require loops to collect information about any one record. Codd's solution to the necessary looping was a set-oriented language, a suggestion that would later spawn the ubiquitous SQL. Using a branch of mathematics known as tuple calculus, he demonstrated that such a system could support all the operations of normal databases (inserting, updating etc.) as well as providing a simple system for finding and returning sets of data in a single operation. | What is used to create the problem of looping? | What is used to create the problem of looping? | [
"What is used to create the problem of looping?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7518 | 5a8c4347fd22b3001a8d8675 | Database | Just as the navigational approach would require programs to loop in order to collect records, the relational approach would require loops to collect information about any one record. Codd's solution to the necessary looping was a set-oriented language, a suggestion that would later spawn the ubiquitous SQL. Using a branch of mathematics known as tuple calculus, he demonstrated that such a system could support all the operations of normal databases (inserting, updating etc.) as well as providing a simple system for finding and returning sets of data in a single operation. | What computer language lost popularity as a result of the looping problem? | What computer language lost popularity as a result of the looping problem? | [
"What computer language lost popularity as a result of the looping problem?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7519 | 5a8c4347fd22b3001a8d8676 | Database | Just as the navigational approach would require programs to loop in order to collect records, the relational approach would require loops to collect information about any one record. Codd's solution to the necessary looping was a set-oriented language, a suggestion that would later spawn the ubiquitous SQL. Using a branch of mathematics known as tuple calculus, he demonstrated that such a system could support all the operations of normal databases (inserting, updating etc.) as well as providing a simple system for finding and returning sets of data in a single operation. | What type of physics was used to create a system to find data sets? | What type of physics was used to create a system to find data sets? | [
"What type of physics was used to create a system to find data sets?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7520 | 5a8c4347fd22b3001a8d8677 | Database | Just as the navigational approach would require programs to loop in order to collect records, the relational approach would require loops to collect information about any one record. Codd's solution to the necessary looping was a set-oriented language, a suggestion that would later spawn the ubiquitous SQL. Using a branch of mathematics known as tuple calculus, he demonstrated that such a system could support all the operations of normal databases (inserting, updating etc.) as well as providing a simple system for finding and returning sets of data in a single operation. | Who used tuple calculus to hide the functionality of databases? | Who used tuple calculus to hide the functionality of databases? | [
"Who used tuple calculus to hide the functionality of databases?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7521 | 572f72aeb2c2fd1400568137 | Database | Codd's paper was picked up by two people at Berkeley, Eugene Wong and Michael Stonebraker. They started a project known as INGRES using funding that had already been allocated for a geographical database project and student programmers to produce code. Beginning in 1973, INGRES delivered its first test products which were generally ready for widespread use in 1979. INGRES was similar to System R in a number of ways, including the use of a "language" for data access, known as QUEL. Over time, INGRES moved to the emerging SQL standard. | Who used Codd's paper at Berkeley to improve a geographical database? | Who used Codd's paper at Berkeley to improve a geographical database? | [
"Who used Codd's paper at Berkeley to improve a geographical database?"
] | {
"text": [
"Eugene Wong and Michael Stonebraker"
],
"answer_start": [
54
]
} |
gem-squad_v2-train-7522 | 572f72aeb2c2fd1400568138 | Database | Codd's paper was picked up by two people at Berkeley, Eugene Wong and Michael Stonebraker. They started a project known as INGRES using funding that had already been allocated for a geographical database project and student programmers to produce code. Beginning in 1973, INGRES delivered its first test products which were generally ready for widespread use in 1979. INGRES was similar to System R in a number of ways, including the use of a "language" for data access, known as QUEL. Over time, INGRES moved to the emerging SQL standard. | What was the name of the project to create a geographical database? | What was the name of the project to create a geographical database? | [
"What was the name of the project to create a geographical database?"
] | {
"text": [
"INGRES"
],
"answer_start": [
272
]
} |
gem-squad_v2-train-7523 | 572f72aeb2c2fd1400568139 | Database | Codd's paper was picked up by two people at Berkeley, Eugene Wong and Michael Stonebraker. They started a project known as INGRES using funding that had already been allocated for a geographical database project and student programmers to produce code. Beginning in 1973, INGRES delivered its first test products which were generally ready for widespread use in 1979. INGRES was similar to System R in a number of ways, including the use of a "language" for data access, known as QUEL. Over time, INGRES moved to the emerging SQL standard. | When was INGRES first tested? | When was INGRES first tested? | [
"When was INGRES first tested?"
] | {
"text": [
"1973"
],
"answer_start": [
266
]
} |
gem-squad_v2-train-7524 | 572f72aeb2c2fd140056813a | Database | Codd's paper was picked up by two people at Berkeley, Eugene Wong and Michael Stonebraker. They started a project known as INGRES using funding that had already been allocated for a geographical database project and student programmers to produce code. Beginning in 1973, INGRES delivered its first test products which were generally ready for widespread use in 1979. INGRES was similar to System R in a number of ways, including the use of a "language" for data access, known as QUEL. Over time, INGRES moved to the emerging SQL standard. | What computer language was used in INGRES to access data? | What computer language was used in INGRES to access data? | [
"What computer language was used in INGRES to access data?"
] | {
"text": [
"QUEL"
],
"answer_start": [
480
]
} |
gem-squad_v2-train-7525 | 572f72aeb2c2fd140056813b | Database | Codd's paper was picked up by two people at Berkeley, Eugene Wong and Michael Stonebraker. They started a project known as INGRES using funding that had already been allocated for a geographical database project and student programmers to produce code. Beginning in 1973, INGRES delivered its first test products which were generally ready for widespread use in 1979. INGRES was similar to System R in a number of ways, including the use of a "language" for data access, known as QUEL. Over time, INGRES moved to the emerging SQL standard. | Is QUEL still used to access data in INGRES? | Is QUEL still used to access data in INGRES? | [
"Is QUEL still used to access data in INGRES?"
] | {
"text": [
"INGRES moved to the emerging SQL standard"
],
"answer_start": [
497
]
} |
gem-squad_v2-train-7526 | 5a8c43befd22b3001a8d867d | Database | Codd's paper was picked up by two people at Berkeley, Eugene Wong and Michael Stonebraker. They started a project known as INGRES using funding that had already been allocated for a geographical database project and student programmers to produce code. Beginning in 1973, INGRES delivered its first test products which were generally ready for widespread use in 1979. INGRES was similar to System R in a number of ways, including the use of a "language" for data access, known as QUEL. Over time, INGRES moved to the emerging SQL standard. | Who used Codd's paper at Yale to improve a geographical database? | Who used Codd's paper at Yale to improve a geographical database? | [
"Who used Codd's paper at Yale to improve a geographical database?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7527 | 5a8c43befd22b3001a8d867e | Database | Codd's paper was picked up by two people at Berkeley, Eugene Wong and Michael Stonebraker. They started a project known as INGRES using funding that had already been allocated for a geographical database project and student programmers to produce code. Beginning in 1973, INGRES delivered its first test products which were generally ready for widespread use in 1979. INGRES was similar to System R in a number of ways, including the use of a "language" for data access, known as QUEL. Over time, INGRES moved to the emerging SQL standard. | What was the name of the project to steal a geographical database? | What was the name of the project to steal a geographical database? | [
"What was the name of the project to steal a geographical database?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7528 | 5a8c43befd22b3001a8d867f | Database | Codd's paper was picked up by two people at Berkeley, Eugene Wong and Michael Stonebraker. They started a project known as INGRES using funding that had already been allocated for a geographical database project and student programmers to produce code. Beginning in 1973, INGRES delivered its first test products which were generally ready for widespread use in 1979. INGRES was similar to System R in a number of ways, including the use of a "language" for data access, known as QUEL. Over time, INGRES moved to the emerging SQL standard. | When was INGRES first avoided? | When was INGRES first avoided? | [
"When was INGRES first avoided?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7529 | 5a8c43befd22b3001a8d8680 | Database | Codd's paper was picked up by two people at Berkeley, Eugene Wong and Michael Stonebraker. They started a project known as INGRES using funding that had already been allocated for a geographical database project and student programmers to produce code. Beginning in 1973, INGRES delivered its first test products which were generally ready for widespread use in 1979. INGRES was similar to System R in a number of ways, including the use of a "language" for data access, known as QUEL. Over time, INGRES moved to the emerging SQL standard. | What computer language was used in INGRES to fabricate data? | What computer language was used in INGRES to fabricate data? | [
"What computer language was used in INGRES to fabricate data?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7530 | 5a8c43befd22b3001a8d8681 | Database | Codd's paper was picked up by two people at Berkeley, Eugene Wong and Michael Stonebraker. They started a project known as INGRES using funding that had already been allocated for a geographical database project and student programmers to produce code. Beginning in 1973, INGRES delivered its first test products which were generally ready for widespread use in 1979. INGRES was similar to System R in a number of ways, including the use of a "language" for data access, known as QUEL. Over time, INGRES moved to the emerging SQL standard. | What year did INGRES stop widespread use? | What year did INGRES stop widespread use? | [
"What year did INGRES stop widespread use?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7531 | 572f73dfb2c2fd1400568141 | Database | Another approach to hardware support for database management was ICL's CAFS accelerator, a hardware disk controller with programmable search capabilities. In the long term, these efforts were generally unsuccessful because specialized database machines could not keep pace with the rapid development and progress of general-purpose computers. Thus most database systems nowadays are software systems running on general-purpose hardware, using general-purpose computer data storage. However this idea is still pursued for certain applications by some companies like Netezza and Oracle (Exadata). | What is a CAFS accelerator? | What is a CAFS accelerator? | [
"What is a CAFS accelerator?"
] | {
"text": [
"a hardware disk controller with programmable search capabilities"
],
"answer_start": [
89
]
} |
gem-squad_v2-train-7532 | 572f73dfb2c2fd1400568142 | Database | Another approach to hardware support for database management was ICL's CAFS accelerator, a hardware disk controller with programmable search capabilities. In the long term, these efforts were generally unsuccessful because specialized database machines could not keep pace with the rapid development and progress of general-purpose computers. Thus most database systems nowadays are software systems running on general-purpose hardware, using general-purpose computer data storage. However this idea is still pursued for certain applications by some companies like Netezza and Oracle (Exadata). | Did the CAFS accelerator work as planned? | Did the CAFS accelerator work as planned? | [
"Did the CAFS accelerator work as planned?"
] | {
"text": [
"efforts were generally unsuccessful"
],
"answer_start": [
179
]
} |
gem-squad_v2-train-7533 | 572f73dfb2c2fd1400568143 | Database | Another approach to hardware support for database management was ICL's CAFS accelerator, a hardware disk controller with programmable search capabilities. In the long term, these efforts were generally unsuccessful because specialized database machines could not keep pace with the rapid development and progress of general-purpose computers. Thus most database systems nowadays are software systems running on general-purpose hardware, using general-purpose computer data storage. However this idea is still pursued for certain applications by some companies like Netezza and Oracle (Exadata). | How are today's database systems run? | How are today's database systems run? | [
"How are today's database systems run?"
] | {
"text": [
"general-purpose hardware"
],
"answer_start": [
411
]
} |
gem-squad_v2-train-7534 | 572f73dfb2c2fd1400568144 | Database | Another approach to hardware support for database management was ICL's CAFS accelerator, a hardware disk controller with programmable search capabilities. In the long term, these efforts were generally unsuccessful because specialized database machines could not keep pace with the rapid development and progress of general-purpose computers. Thus most database systems nowadays are software systems running on general-purpose hardware, using general-purpose computer data storage. However this idea is still pursued for certain applications by some companies like Netezza and Oracle (Exadata). | Name a company that is still working on the CAFS accellerator? | Name a company that is still working on the CAFS accellerator? | [
"Name a company that is still working on the CAFS accellerator?"
] | {
"text": [
"Netezza and Oracle (Exadata)"
],
"answer_start": [
565
]
} |
gem-squad_v2-train-7535 | 5a8c4494fd22b3001a8d8687 | Database | Another approach to hardware support for database management was ICL's CAFS accelerator, a hardware disk controller with programmable search capabilities. In the long term, these efforts were generally unsuccessful because specialized database machines could not keep pace with the rapid development and progress of general-purpose computers. Thus most database systems nowadays are software systems running on general-purpose hardware, using general-purpose computer data storage. However this idea is still pursued for certain applications by some companies like Netezza and Oracle (Exadata). | What is a CAFS decelerator? | What is a CAFS decelerator? | [
"What is a CAFS decelerator?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7536 | 5a8c4494fd22b3001a8d8688 | Database | Another approach to hardware support for database management was ICL's CAFS accelerator, a hardware disk controller with programmable search capabilities. In the long term, these efforts were generally unsuccessful because specialized database machines could not keep pace with the rapid development and progress of general-purpose computers. Thus most database systems nowadays are software systems running on general-purpose hardware, using general-purpose computer data storage. However this idea is still pursued for certain applications by some companies like Netezza and Oracle (Exadata). | What is no longer used in modern database systems? | What is no longer used in modern database systems? | [
"What is no longer used in modern database systems?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7537 | 5a8c4494fd22b3001a8d8689 | Database | Another approach to hardware support for database management was ICL's CAFS accelerator, a hardware disk controller with programmable search capabilities. In the long term, these efforts were generally unsuccessful because specialized database machines could not keep pace with the rapid development and progress of general-purpose computers. Thus most database systems nowadays are software systems running on general-purpose hardware, using general-purpose computer data storage. However this idea is still pursued for certain applications by some companies like Netezza and Oracle (Exadata). | What companies still work on the CAFS decelerator? | What companies still work on the CAFS decelerator? | [
"What companies still work on the CAFS decelerator?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7538 | 5a8c4494fd22b3001a8d868a | Database | Another approach to hardware support for database management was ICL's CAFS accelerator, a hardware disk controller with programmable search capabilities. In the long term, these efforts were generally unsuccessful because specialized database machines could not keep pace with the rapid development and progress of general-purpose computers. Thus most database systems nowadays are software systems running on general-purpose hardware, using general-purpose computer data storage. However this idea is still pursued for certain applications by some companies like Netezza and Oracle (Exadata). | What are rarely seen nowadays? | What are rarely seen nowadays? | [
"What are rarely seen nowadays?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7539 | 5a8c4494fd22b3001a8d868b | Database | Another approach to hardware support for database management was ICL's CAFS accelerator, a hardware disk controller with programmable search capabilities. In the long term, these efforts were generally unsuccessful because specialized database machines could not keep pace with the rapid development and progress of general-purpose computers. Thus most database systems nowadays are software systems running on general-purpose hardware, using general-purpose computer data storage. However this idea is still pursued for certain applications by some companies like Netezza and Oracle (Exadata). | What was a failed approach to hardware support for database management? | What was a failed approach to hardware support for database management? | [
"What was a failed approach to hardware support for database management?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7540 | 572f753604bcaa1900d76989 | Database | IBM started working on a prototype system loosely based on Codd's concepts as System R in the early 1970s. The first version was ready in 1974/5, and work then started on multi-table systems in which the data could be split so that all of the data for a record (some of which is optional) did not have to be stored in a single large "chunk". Subsequent multi-user versions were tested by customers in 1978 and 1979, by which time a standardized query language – SQL[citation needed] – had been added. Codd's ideas were establishing themselves as both workable and superior to CODASYL, pushing IBM to develop a true production version of System R, known as SQL/DS, and, later, Database 2 (DB2). | What is the system IBM created using Codd's research? | What is the system IBM created using Codd's research? | [
"What is the system IBM created using Codd's research?"
] | {
"text": [
"System R"
],
"answer_start": [
78
]
} |
gem-squad_v2-train-7541 | 572f753604bcaa1900d7698a | Database | IBM started working on a prototype system loosely based on Codd's concepts as System R in the early 1970s. The first version was ready in 1974/5, and work then started on multi-table systems in which the data could be split so that all of the data for a record (some of which is optional) did not have to be stored in a single large "chunk". Subsequent multi-user versions were tested by customers in 1978 and 1979, by which time a standardized query language – SQL[citation needed] – had been added. Codd's ideas were establishing themselves as both workable and superior to CODASYL, pushing IBM to develop a true production version of System R, known as SQL/DS, and, later, Database 2 (DB2). | When was IBM's system released? | When was IBM's system released? | [
"When was IBM's system released?"
] | {
"text": [
"1974/5"
],
"answer_start": [
138
]
} |
gem-squad_v2-train-7542 | 572f753604bcaa1900d7698b | Database | IBM started working on a prototype system loosely based on Codd's concepts as System R in the early 1970s. The first version was ready in 1974/5, and work then started on multi-table systems in which the data could be split so that all of the data for a record (some of which is optional) did not have to be stored in a single large "chunk". Subsequent multi-user versions were tested by customers in 1978 and 1979, by which time a standardized query language – SQL[citation needed] – had been added. Codd's ideas were establishing themselves as both workable and superior to CODASYL, pushing IBM to develop a true production version of System R, known as SQL/DS, and, later, Database 2 (DB2). | What did System R work on to change the way data was stored? | What did System R work on to change the way data was stored? | [
"What did System R work on to change the way data was stored?"
] | {
"text": [
"multi-table systems"
],
"answer_start": [
171
]
} |
gem-squad_v2-train-7543 | 572f753604bcaa1900d7698c | Database | IBM started working on a prototype system loosely based on Codd's concepts as System R in the early 1970s. The first version was ready in 1974/5, and work then started on multi-table systems in which the data could be split so that all of the data for a record (some of which is optional) did not have to be stored in a single large "chunk". Subsequent multi-user versions were tested by customers in 1978 and 1979, by which time a standardized query language – SQL[citation needed] – had been added. Codd's ideas were establishing themselves as both workable and superior to CODASYL, pushing IBM to develop a true production version of System R, known as SQL/DS, and, later, Database 2 (DB2). | When customers first tested IBM's system, what computer language had been added? | When customers first tested IBM's system, what computer language had been added? | [
"When customers first tested IBM's system, what computer language had been added? "
] | {
"text": [
"SQL"
],
"answer_start": [
462
]
} |
gem-squad_v2-train-7544 | 572f753604bcaa1900d7698d | Database | IBM started working on a prototype system loosely based on Codd's concepts as System R in the early 1970s. The first version was ready in 1974/5, and work then started on multi-table systems in which the data could be split so that all of the data for a record (some of which is optional) did not have to be stored in a single large "chunk". Subsequent multi-user versions were tested by customers in 1978 and 1979, by which time a standardized query language – SQL[citation needed] – had been added. Codd's ideas were establishing themselves as both workable and superior to CODASYL, pushing IBM to develop a true production version of System R, known as SQL/DS, and, later, Database 2 (DB2). | What was the name of the database product created by IBM? | What was the name of the database product created by IBM? | [
"What was the name of the database product created by IBM?"
] | {
"text": [
"SQL/DS, and, later, Database 2 (DB2)"
],
"answer_start": [
656
]
} |
gem-squad_v2-train-7545 | 5a8c452afd22b3001a8d8691 | Database | IBM started working on a prototype system loosely based on Codd's concepts as System R in the early 1970s. The first version was ready in 1974/5, and work then started on multi-table systems in which the data could be split so that all of the data for a record (some of which is optional) did not have to be stored in a single large "chunk". Subsequent multi-user versions were tested by customers in 1978 and 1979, by which time a standardized query language – SQL[citation needed] – had been added. Codd's ideas were establishing themselves as both workable and superior to CODASYL, pushing IBM to develop a true production version of System R, known as SQL/DS, and, later, Database 2 (DB2). | What is the system IBM lost using Codd's research? | What is the system IBM lost using Codd's research? | [
"What is the system IBM lost using Codd's research?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7546 | 5a8c452afd22b3001a8d8692 | Database | IBM started working on a prototype system loosely based on Codd's concepts as System R in the early 1970s. The first version was ready in 1974/5, and work then started on multi-table systems in which the data could be split so that all of the data for a record (some of which is optional) did not have to be stored in a single large "chunk". Subsequent multi-user versions were tested by customers in 1978 and 1979, by which time a standardized query language – SQL[citation needed] – had been added. Codd's ideas were establishing themselves as both workable and superior to CODASYL, pushing IBM to develop a true production version of System R, known as SQL/DS, and, later, Database 2 (DB2). | When was IBM's system stolen? | When was IBM's system stolen? | [
"When was IBM's system stolen?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7547 | 5a8c452afd22b3001a8d8693 | Database | IBM started working on a prototype system loosely based on Codd's concepts as System R in the early 1970s. The first version was ready in 1974/5, and work then started on multi-table systems in which the data could be split so that all of the data for a record (some of which is optional) did not have to be stored in a single large "chunk". Subsequent multi-user versions were tested by customers in 1978 and 1979, by which time a standardized query language – SQL[citation needed] – had been added. Codd's ideas were establishing themselves as both workable and superior to CODASYL, pushing IBM to develop a true production version of System R, known as SQL/DS, and, later, Database 2 (DB2). | What did System R avoid to change the way data was stored? | What did System R avoid to change the way data was stored? | [
"What did System R avoid to change the way data was stored?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7548 | 5a8c452afd22b3001a8d8694 | Database | IBM started working on a prototype system loosely based on Codd's concepts as System R in the early 1970s. The first version was ready in 1974/5, and work then started on multi-table systems in which the data could be split so that all of the data for a record (some of which is optional) did not have to be stored in a single large "chunk". Subsequent multi-user versions were tested by customers in 1978 and 1979, by which time a standardized query language – SQL[citation needed] – had been added. Codd's ideas were establishing themselves as both workable and superior to CODASYL, pushing IBM to develop a true production version of System R, known as SQL/DS, and, later, Database 2 (DB2). | When customers first tested IBM's system, what computer language had been removed? | When customers first tested IBM's system, what computer language had been removed? | [
"When customers first tested IBM's system, what computer language had been removed?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7549 | 5a8c452afd22b3001a8d8695 | Database | IBM started working on a prototype system loosely based on Codd's concepts as System R in the early 1970s. The first version was ready in 1974/5, and work then started on multi-table systems in which the data could be split so that all of the data for a record (some of which is optional) did not have to be stored in a single large "chunk". Subsequent multi-user versions were tested by customers in 1978 and 1979, by which time a standardized query language – SQL[citation needed] – had been added. Codd's ideas were establishing themselves as both workable and superior to CODASYL, pushing IBM to develop a true production version of System R, known as SQL/DS, and, later, Database 2 (DB2). | What was the name of the database product created by IBN? | What was the name of the database product created by IBN? | [
"What was the name of the database product created by IBN?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7550 | 572f762404bcaa1900d769a3 | Database | The 1980s ushered in the age of desktop computing. The new computers empowered their users with spreadsheets like Lotus 1-2-3 and database software like dBASE. The dBASE product was lightweight and easy for any computer user to understand out of the box. C. Wayne Ratliff the creator of dBASE stated: "dBASE was different from programs like BASIC, C, FORTRAN, and COBOL in that a lot of the dirty work had already been done. The data manipulation is done by dBASE instead of by the user, so the user can concentrate on what he is doing, rather than having to mess with the dirty details of opening, reading, and closing files, and managing space allocation." dBASE was one of the top selling software titles in the 1980s and early 1990s. | Who created dBASE? | Who created dBASE? | [
"Who created dBASE?"
] | {
"text": [
"C. Wayne Ratliff"
],
"answer_start": [
255
]
} |
gem-squad_v2-train-7551 | 572f762404bcaa1900d769a4 | Database | The 1980s ushered in the age of desktop computing. The new computers empowered their users with spreadsheets like Lotus 1-2-3 and database software like dBASE. The dBASE product was lightweight and easy for any computer user to understand out of the box. C. Wayne Ratliff the creator of dBASE stated: "dBASE was different from programs like BASIC, C, FORTRAN, and COBOL in that a lot of the dirty work had already been done. The data manipulation is done by dBASE instead of by the user, so the user can concentrate on what he is doing, rather than having to mess with the dirty details of opening, reading, and closing files, and managing space allocation." dBASE was one of the top selling software titles in the 1980s and early 1990s. | Why was dBASE successful? | Why was dBASE successful? | [
"Why was dBASE successful?"
] | {
"text": [
"lightweight and easy for any computer user to understand out of the box"
],
"answer_start": [
182
]
} |
gem-squad_v2-train-7552 | 572f762404bcaa1900d769a5 | Database | The 1980s ushered in the age of desktop computing. The new computers empowered their users with spreadsheets like Lotus 1-2-3 and database software like dBASE. The dBASE product was lightweight and easy for any computer user to understand out of the box. C. Wayne Ratliff the creator of dBASE stated: "dBASE was different from programs like BASIC, C, FORTRAN, and COBOL in that a lot of the dirty work had already been done. The data manipulation is done by dBASE instead of by the user, so the user can concentrate on what he is doing, rather than having to mess with the dirty details of opening, reading, and closing files, and managing space allocation." dBASE was one of the top selling software titles in the 1980s and early 1990s. | Why was dBASE unique? | Why was dBASE unique? | [
"Why was dBASE unique?"
] | {
"text": [
"data manipulation is done by dBASE"
],
"answer_start": [
429
]
} |
gem-squad_v2-train-7553 | 572f762404bcaa1900d769a6 | Database | The 1980s ushered in the age of desktop computing. The new computers empowered their users with spreadsheets like Lotus 1-2-3 and database software like dBASE. The dBASE product was lightweight and easy for any computer user to understand out of the box. C. Wayne Ratliff the creator of dBASE stated: "dBASE was different from programs like BASIC, C, FORTRAN, and COBOL in that a lot of the dirty work had already been done. The data manipulation is done by dBASE instead of by the user, so the user can concentrate on what he is doing, rather than having to mess with the dirty details of opening, reading, and closing files, and managing space allocation." dBASE was one of the top selling software titles in the 1980s and early 1990s. | What is a benefit of using dBASE? | What is a benefit of using dBASE? | [
"What is a benefit of using dBASE?"
] | {
"text": [
"managing space allocation"
],
"answer_start": [
631
]
} |
gem-squad_v2-train-7554 | 5a8c7a0efd22b3001a8d88a6 | Database | The 1980s ushered in the age of desktop computing. The new computers empowered their users with spreadsheets like Lotus 1-2-3 and database software like dBASE. The dBASE product was lightweight and easy for any computer user to understand out of the box. C. Wayne Ratliff the creator of dBASE stated: "dBASE was different from programs like BASIC, C, FORTRAN, and COBOL in that a lot of the dirty work had already been done. The data manipulation is done by dBASE instead of by the user, so the user can concentrate on what he is doing, rather than having to mess with the dirty details of opening, reading, and closing files, and managing space allocation." dBASE was one of the top selling software titles in the 1980s and early 1990s. | Who created BASE? | Who created BASE? | [
"Who created BASE?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7555 | 5a8c7a0efd22b3001a8d88a7 | Database | The 1980s ushered in the age of desktop computing. The new computers empowered their users with spreadsheets like Lotus 1-2-3 and database software like dBASE. The dBASE product was lightweight and easy for any computer user to understand out of the box. C. Wayne Ratliff the creator of dBASE stated: "dBASE was different from programs like BASIC, C, FORTRAN, and COBOL in that a lot of the dirty work had already been done. The data manipulation is done by dBASE instead of by the user, so the user can concentrate on what he is doing, rather than having to mess with the dirty details of opening, reading, and closing files, and managing space allocation." dBASE was one of the top selling software titles in the 1980s and early 1990s. | Why was dBASE unsuccessful? | Why was dBASE unsuccessful? | [
"Why was dBASE unsuccessful?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7556 | 5a8c7a0efd22b3001a8d88a8 | Database | The 1980s ushered in the age of desktop computing. The new computers empowered their users with spreadsheets like Lotus 1-2-3 and database software like dBASE. The dBASE product was lightweight and easy for any computer user to understand out of the box. C. Wayne Ratliff the creator of dBASE stated: "dBASE was different from programs like BASIC, C, FORTRAN, and COBOL in that a lot of the dirty work had already been done. The data manipulation is done by dBASE instead of by the user, so the user can concentrate on what he is doing, rather than having to mess with the dirty details of opening, reading, and closing files, and managing space allocation." dBASE was one of the top selling software titles in the 1980s and early 1990s. | Why was dBASE considered common? | Why was dBASE considered common? | [
"Why was dBASE considered common?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7557 | 5a8c7a0efd22b3001a8d88a9 | Database | The 1980s ushered in the age of desktop computing. The new computers empowered their users with spreadsheets like Lotus 1-2-3 and database software like dBASE. The dBASE product was lightweight and easy for any computer user to understand out of the box. C. Wayne Ratliff the creator of dBASE stated: "dBASE was different from programs like BASIC, C, FORTRAN, and COBOL in that a lot of the dirty work had already been done. The data manipulation is done by dBASE instead of by the user, so the user can concentrate on what he is doing, rather than having to mess with the dirty details of opening, reading, and closing files, and managing space allocation." dBASE was one of the top selling software titles in the 1980s and early 1990s. | What is the only benefit of using dBASE? | What is the only benefit of using dBASE? | [
"What is the only benefit of using dBASE?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7558 | 5a8c7a0efd22b3001a8d88aa | Database | The 1980s ushered in the age of desktop computing. The new computers empowered their users with spreadsheets like Lotus 1-2-3 and database software like dBASE. The dBASE product was lightweight and easy for any computer user to understand out of the box. C. Wayne Ratliff the creator of dBASE stated: "dBASE was different from programs like BASIC, C, FORTRAN, and COBOL in that a lot of the dirty work had already been done. The data manipulation is done by dBASE instead of by the user, so the user can concentrate on what he is doing, rather than having to mess with the dirty details of opening, reading, and closing files, and managing space allocation." dBASE was one of the top selling software titles in the 1980s and early 1990s. | When was BASE the top selling software title? | When was BASE the top selling software title? | [
"When was BASE the top selling software title?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7559 | 572f77f4b2c2fd1400568159 | Database | The 1990s, along with a rise in object-oriented programming, saw a growth in how data in various databases were handled. Programmers and designers began to treat the data in their databases as objects. That is to say that if a person's data were in a database, that person's attributes, such as their address, phone number, and age, were now considered to belong to that person instead of being extraneous data. This allows for relations between data to be relations to objects and their attributes and not to individual fields. The term "object-relational impedance mismatch" described the inconvenience of translating between programmed objects and database tables. Object databases and object-relational databases attempt to solve this problem by providing an object-oriented language (sometimes as extensions to SQL) that programmers can use as alternative to purely relational SQL. On the programming side, libraries known as object-relational mappings (ORMs) attempt to solve the same problem. | In the 1990s, what type of programming changed the handling of databases? | In the 1990s, what type of programming changed the handling of databases? | [
"In the 1990s, what type of programming changed the handling of databases?"
] | {
"text": [
"object-oriented"
],
"answer_start": [
32
]
} |
gem-squad_v2-train-7560 | 572f77f4b2c2fd140056815a | Database | The 1990s, along with a rise in object-oriented programming, saw a growth in how data in various databases were handled. Programmers and designers began to treat the data in their databases as objects. That is to say that if a person's data were in a database, that person's attributes, such as their address, phone number, and age, were now considered to belong to that person instead of being extraneous data. This allows for relations between data to be relations to objects and their attributes and not to individual fields. The term "object-relational impedance mismatch" described the inconvenience of translating between programmed objects and database tables. Object databases and object-relational databases attempt to solve this problem by providing an object-oriented language (sometimes as extensions to SQL) that programmers can use as alternative to purely relational SQL. On the programming side, libraries known as object-relational mappings (ORMs) attempt to solve the same problem. | What term is used for the difficulty in database table and programmed object translation? | What term is used for the difficulty in database table and programmed object translation? | [
"What term is used for the difficulty in database table and programmed object translation?"
] | {
"text": [
"object-relational impedance mismatch"
],
"answer_start": [
539
]
} |
gem-squad_v2-train-7561 | 572f77f4b2c2fd140056815b | Database | The 1990s, along with a rise in object-oriented programming, saw a growth in how data in various databases were handled. Programmers and designers began to treat the data in their databases as objects. That is to say that if a person's data were in a database, that person's attributes, such as their address, phone number, and age, were now considered to belong to that person instead of being extraneous data. This allows for relations between data to be relations to objects and their attributes and not to individual fields. The term "object-relational impedance mismatch" described the inconvenience of translating between programmed objects and database tables. Object databases and object-relational databases attempt to solve this problem by providing an object-oriented language (sometimes as extensions to SQL) that programmers can use as alternative to purely relational SQL. On the programming side, libraries known as object-relational mappings (ORMs) attempt to solve the same problem. | How is the problem of object-relational impedance mismatch corrected? | How is the problem of object-relational impedance mismatch corrected? | [
"How is the problem of object-relational impedance mismatch corrected?"
] | {
"text": [
"object-oriented language"
],
"answer_start": [
763
]
} |
gem-squad_v2-train-7562 | 572f77f4b2c2fd140056815c | Database | The 1990s, along with a rise in object-oriented programming, saw a growth in how data in various databases were handled. Programmers and designers began to treat the data in their databases as objects. That is to say that if a person's data were in a database, that person's attributes, such as their address, phone number, and age, were now considered to belong to that person instead of being extraneous data. This allows for relations between data to be relations to objects and their attributes and not to individual fields. The term "object-relational impedance mismatch" described the inconvenience of translating between programmed objects and database tables. Object databases and object-relational databases attempt to solve this problem by providing an object-oriented language (sometimes as extensions to SQL) that programmers can use as alternative to purely relational SQL. On the programming side, libraries known as object-relational mappings (ORMs) attempt to solve the same problem. | What is the library programmers use to solve object-relational impedance mismatch? | What is the library programmers use to solve object-relational impedance mismatch? | [
"What is the library programmers use to solve object-relational impedance mismatch?"
] | {
"text": [
"object-relational mappings (ORMs)"
],
"answer_start": [
931
]
} |
gem-squad_v2-train-7563 | 5a8c839afd22b3001a8d89d6 | Database | The 1990s, along with a rise in object-oriented programming, saw a growth in how data in various databases were handled. Programmers and designers began to treat the data in their databases as objects. That is to say that if a person's data were in a database, that person's attributes, such as their address, phone number, and age, were now considered to belong to that person instead of being extraneous data. This allows for relations between data to be relations to objects and their attributes and not to individual fields. The term "object-relational impedance mismatch" described the inconvenience of translating between programmed objects and database tables. Object databases and object-relational databases attempt to solve this problem by providing an object-oriented language (sometimes as extensions to SQL) that programmers can use as alternative to purely relational SQL. On the programming side, libraries known as object-relational mappings (ORMs) attempt to solve the same problem. | What type of programming did not influence databases? | What type of programming did not influence databases? | [
"What type of programming did not influence databases?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7564 | 5a8c839afd22b3001a8d89d7 | Database | The 1990s, along with a rise in object-oriented programming, saw a growth in how data in various databases were handled. Programmers and designers began to treat the data in their databases as objects. That is to say that if a person's data were in a database, that person's attributes, such as their address, phone number, and age, were now considered to belong to that person instead of being extraneous data. This allows for relations between data to be relations to objects and their attributes and not to individual fields. The term "object-relational impedance mismatch" described the inconvenience of translating between programmed objects and database tables. Object databases and object-relational databases attempt to solve this problem by providing an object-oriented language (sometimes as extensions to SQL) that programmers can use as alternative to purely relational SQL. On the programming side, libraries known as object-relational mappings (ORMs) attempt to solve the same problem. | What term is no longer used for the difficulty in database table and programmed object translation? | What term is no longer used for the difficulty in database table and programmed object translation? | [
"What term is no longer used for the difficulty in database table and programmed object translation?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7565 | 5a8c839afd22b3001a8d89d8 | Database | The 1990s, along with a rise in object-oriented programming, saw a growth in how data in various databases were handled. Programmers and designers began to treat the data in their databases as objects. That is to say that if a person's data were in a database, that person's attributes, such as their address, phone number, and age, were now considered to belong to that person instead of being extraneous data. This allows for relations between data to be relations to objects and their attributes and not to individual fields. The term "object-relational impedance mismatch" described the inconvenience of translating between programmed objects and database tables. Object databases and object-relational databases attempt to solve this problem by providing an object-oriented language (sometimes as extensions to SQL) that programmers can use as alternative to purely relational SQL. On the programming side, libraries known as object-relational mappings (ORMs) attempt to solve the same problem. | How is the problem of object-relational impedance mismatch started? | How is the problem of object-relational impedance mismatch started? | [
"How is the problem of object-relational impedance mismatch started?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7566 | 5a8c839afd22b3001a8d89d9 | Database | The 1990s, along with a rise in object-oriented programming, saw a growth in how data in various databases were handled. Programmers and designers began to treat the data in their databases as objects. That is to say that if a person's data were in a database, that person's attributes, such as their address, phone number, and age, were now considered to belong to that person instead of being extraneous data. This allows for relations between data to be relations to objects and their attributes and not to individual fields. The term "object-relational impedance mismatch" described the inconvenience of translating between programmed objects and database tables. Object databases and object-relational databases attempt to solve this problem by providing an object-oriented language (sometimes as extensions to SQL) that programmers can use as alternative to purely relational SQL. On the programming side, libraries known as object-relational mappings (ORMs) attempt to solve the same problem. | What is the hardware programmers use to solve object-relational impedance mismatch? | What is the hardware programmers use to solve object-relational impedance mismatch? | [
"What is the hardware programmers use to solve object-relational impedance mismatch?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7567 | 572f78f5b2c2fd1400568161 | Database |
XML databases are a type of structured document-oriented database that allows querying based on XML document attributes. XML databases are mostly used in enterprise database management, where XML is being used as the machine-to-machine data interoperability standard. XML database management systems include commercial software MarkLogic and Oracle Berkeley DB XML, and a free use software Clusterpoint Distributed XML/JSON Database. All are enterprise software database platforms and support industry standard ACID-compliant transaction processing with strong database consistency characteristics and high level of database security. | What kind of database is XML? | What kind of database is XML? | [
"What kind of database is XML?"
] | {
"text": [
"structured document-oriented database"
],
"answer_start": [
29
]
} |
gem-squad_v2-train-7568 | 572f78f5b2c2fd1400568162 | Database |
XML databases are a type of structured document-oriented database that allows querying based on XML document attributes. XML databases are mostly used in enterprise database management, where XML is being used as the machine-to-machine data interoperability standard. XML database management systems include commercial software MarkLogic and Oracle Berkeley DB XML, and a free use software Clusterpoint Distributed XML/JSON Database. All are enterprise software database platforms and support industry standard ACID-compliant transaction processing with strong database consistency characteristics and high level of database security. | Where are XML databases frequently used? | Where are XML databases frequently used? | [
"Where are XML databases frequently used?"
] | {
"text": [
"enterprise database management"
],
"answer_start": [
155
]
} |
gem-squad_v2-train-7569 | 572f78f5b2c2fd1400568163 | Database |
XML databases are a type of structured document-oriented database that allows querying based on XML document attributes. XML databases are mostly used in enterprise database management, where XML is being used as the machine-to-machine data interoperability standard. XML database management systems include commercial software MarkLogic and Oracle Berkeley DB XML, and a free use software Clusterpoint Distributed XML/JSON Database. All are enterprise software database platforms and support industry standard ACID-compliant transaction processing with strong database consistency characteristics and high level of database security. | How is XML used in enterprise database management? | How is XML used in enterprise database management? | [
"How is XML used in enterprise database management?"
] | {
"text": [
"machine-to-machine data"
],
"answer_start": [
218
]
} |
gem-squad_v2-train-7570 | 572f78f5b2c2fd1400568164 | Database |
XML databases are a type of structured document-oriented database that allows querying based on XML document attributes. XML databases are mostly used in enterprise database management, where XML is being used as the machine-to-machine data interoperability standard. XML database management systems include commercial software MarkLogic and Oracle Berkeley DB XML, and a free use software Clusterpoint Distributed XML/JSON Database. All are enterprise software database platforms and support industry standard ACID-compliant transaction processing with strong database consistency characteristics and high level of database security. | What type of processing is used in enterprise database software? | What type of processing is used in enterprise database software? | [
"What type of processing is used in enterprise database software?"
] | {
"text": [
"ACID-compliant transaction processing"
],
"answer_start": [
512
]
} |
gem-squad_v2-train-7571 | 5a8c840bfd22b3001a8d89de | Database |
XML databases are a type of structured document-oriented database that allows querying based on XML document attributes. XML databases are mostly used in enterprise database management, where XML is being used as the machine-to-machine data interoperability standard. XML database management systems include commercial software MarkLogic and Oracle Berkeley DB XML, and a free use software Clusterpoint Distributed XML/JSON Database. All are enterprise software database platforms and support industry standard ACID-compliant transaction processing with strong database consistency characteristics and high level of database security. | What kind of database is ZML? | What kind of database is ZML? | [
"What kind of database is ZML?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7572 | 5a8c840bfd22b3001a8d89df | Database |
XML databases are a type of structured document-oriented database that allows querying based on XML document attributes. XML databases are mostly used in enterprise database management, where XML is being used as the machine-to-machine data interoperability standard. XML database management systems include commercial software MarkLogic and Oracle Berkeley DB XML, and a free use software Clusterpoint Distributed XML/JSON Database. All are enterprise software database platforms and support industry standard ACID-compliant transaction processing with strong database consistency characteristics and high level of database security. | Where are XML databases never used? | Where are XML databases never used? | [
"Where are XML databases never used?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7573 | 5a8c840bfd22b3001a8d89e0 | Database |
XML databases are a type of structured document-oriented database that allows querying based on XML document attributes. XML databases are mostly used in enterprise database management, where XML is being used as the machine-to-machine data interoperability standard. XML database management systems include commercial software MarkLogic and Oracle Berkeley DB XML, and a free use software Clusterpoint Distributed XML/JSON Database. All are enterprise software database platforms and support industry standard ACID-compliant transaction processing with strong database consistency characteristics and high level of database security. | How is XML bypassed in enterprise database management? | How is XML bypassed in enterprise database management? | [
"How is XML bypassed in enterprise database management?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7574 | 5a8c840bfd22b3001a8d89e1 | Database |
XML databases are a type of structured document-oriented database that allows querying based on XML document attributes. XML databases are mostly used in enterprise database management, where XML is being used as the machine-to-machine data interoperability standard. XML database management systems include commercial software MarkLogic and Oracle Berkeley DB XML, and a free use software Clusterpoint Distributed XML/JSON Database. All are enterprise software database platforms and support industry standard ACID-compliant transaction processing with strong database consistency characteristics and high level of database security. | What type of processing is forbidden in enterprise database software? | What type of processing is forbidden in enterprise database software? | [
"What type of processing is forbidden in enterprise database software?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7575 | 572fa578947a6a140053cb04 | Database | In recent years there was a high demand for massively distributed databases with high partition tolerance but according to the CAP theorem it is impossible for a distributed system to simultaneously provide consistency, availability and partition tolerance guarantees. A distributed system can satisfy any two of these guarantees at the same time, but not all three. For that reason many NoSQL databases are using what is called eventual consistency to provide both availability and partition tolerance guarantees with a reduced level of data consistency. | What explains the difficulty in a system containing availability, consistency, and partition tolerance guarantees? | What explains the difficulty in a system containing availability, consistency, and partition tolerance guarantees? | [
"What explains the difficulty in a system containing availability, consistency, and partition tolerance guarantees?"
] | {
"text": [
"the CAP theorem"
],
"answer_start": [
123
]
} |
gem-squad_v2-train-7576 | 572fa578947a6a140053cb05 | Database | In recent years there was a high demand for massively distributed databases with high partition tolerance but according to the CAP theorem it is impossible for a distributed system to simultaneously provide consistency, availability and partition tolerance guarantees. A distributed system can satisfy any two of these guarantees at the same time, but not all three. For that reason many NoSQL databases are using what is called eventual consistency to provide both availability and partition tolerance guarantees with a reduced level of data consistency. | How many guarantees will most databases tolerate? | How many guarantees will most databases tolerate? | [
"How many guarantees will most databases tolerate?"
] | {
"text": [
"two"
],
"answer_start": [
306
]
} |
gem-squad_v2-train-7577 | 572fa578947a6a140053cb06 | Database | In recent years there was a high demand for massively distributed databases with high partition tolerance but according to the CAP theorem it is impossible for a distributed system to simultaneously provide consistency, availability and partition tolerance guarantees. A distributed system can satisfy any two of these guarantees at the same time, but not all three. For that reason many NoSQL databases are using what is called eventual consistency to provide both availability and partition tolerance guarantees with a reduced level of data consistency. | What is used to offer a balance in guarantees? | What is used to offer a balance in guarantees? | [
"What is used to offer a balance in guarantees?"
] | {
"text": [
"eventual consistency"
],
"answer_start": [
429
]
} |
gem-squad_v2-train-7578 | 5a8c8519fd22b3001a8d89e6 | Database | In recent years there was a high demand for massively distributed databases with high partition tolerance but according to the CAP theorem it is impossible for a distributed system to simultaneously provide consistency, availability and partition tolerance guarantees. A distributed system can satisfy any two of these guarantees at the same time, but not all three. For that reason many NoSQL databases are using what is called eventual consistency to provide both availability and partition tolerance guarantees with a reduced level of data consistency. | What can't explain the difficulty in a system containing availability, consistency, and partition tolerance guarantees? | What can't explain the difficulty in a system containing availability, consistency, and partition tolerance guarantees? | [
"What can't explain the difficulty in a system containing availability, consistency, and partition tolerance guarantees?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7579 | 5a8c8519fd22b3001a8d89e7 | Database | In recent years there was a high demand for massively distributed databases with high partition tolerance but according to the CAP theorem it is impossible for a distributed system to simultaneously provide consistency, availability and partition tolerance guarantees. A distributed system can satisfy any two of these guarantees at the same time, but not all three. For that reason many NoSQL databases are using what is called eventual consistency to provide both availability and partition tolerance guarantees with a reduced level of data consistency. | How many guarantees will most databases destroy? | How many guarantees will most databases destroy? | [
"How many guarantees will most databases destroy?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7580 | 5a8c8519fd22b3001a8d89e8 | Database | In recent years there was a high demand for massively distributed databases with high partition tolerance but according to the CAP theorem it is impossible for a distributed system to simultaneously provide consistency, availability and partition tolerance guarantees. A distributed system can satisfy any two of these guarantees at the same time, but not all three. For that reason many NoSQL databases are using what is called eventual consistency to provide both availability and partition tolerance guarantees with a reduced level of data consistency. | What can satisfy all guarantees at the same time? | What can satisfy all guarantees at the same time? | [
"What can satisfy all guarantees at the same time?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7581 | 5a8c8519fd22b3001a8d89e9 | Database | In recent years there was a high demand for massively distributed databases with high partition tolerance but according to the CAP theorem it is impossible for a distributed system to simultaneously provide consistency, availability and partition tolerance guarantees. A distributed system can satisfy any two of these guarantees at the same time, but not all three. For that reason many NoSQL databases are using what is called eventual consistency to provide both availability and partition tolerance guarantees with a reduced level of data consistency. | What is used to discourage eventual consistency? | What is used to discourage eventual consistency? | [
"What is used to discourage eventual consistency?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7582 | 5a8c8519fd22b3001a8d89ea | Database | In recent years there was a high demand for massively distributed databases with high partition tolerance but according to the CAP theorem it is impossible for a distributed system to simultaneously provide consistency, availability and partition tolerance guarantees. A distributed system can satisfy any two of these guarantees at the same time, but not all three. For that reason many NoSQL databases are using what is called eventual consistency to provide both availability and partition tolerance guarantees with a reduced level of data consistency. | What has had low demand in recent years? | What has had low demand in recent years? | [
"What has had low demand in recent years?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7583 | 572fa97e04bcaa1900d76b79 | Database | The first task of a database designer is to produce a conceptual data model that reflects the structure of the information to be held in the database. A common approach to this is to develop an entity-relationship model, often with the aid of drawing tools. Another popular approach is the Unified Modeling Language. A successful data model will accurately reflect the possible state of the external world being modeled: for example, if people can have more than one phone number, it will allow this information to be captured. Designing a good conceptual data model requires a good understanding of the application domain; it typically involves asking deep questions about the things of interest to an organisation, like "can a customer also be a supplier?", or "if a product is sold with two different forms of packaging, are those the same product or different products?", or "if a plane flies from New York to Dubai via Frankfurt, is that one flight or two (or maybe even three)?". The answers to these questions establish definitions of the terminology used for entities (customers, products, flights, flight segments) and their relationships and attributes. | What should a conceptual data model do? | What should a conceptual data model do? | [
"What should a conceptual data model do?"
] | {
"text": [
"reflects the structure of the information to be held"
],
"answer_start": [
81
]
} |
gem-squad_v2-train-7584 | 572fa97e04bcaa1900d76b7a | Database | The first task of a database designer is to produce a conceptual data model that reflects the structure of the information to be held in the database. A common approach to this is to develop an entity-relationship model, often with the aid of drawing tools. Another popular approach is the Unified Modeling Language. A successful data model will accurately reflect the possible state of the external world being modeled: for example, if people can have more than one phone number, it will allow this information to be captured. Designing a good conceptual data model requires a good understanding of the application domain; it typically involves asking deep questions about the things of interest to an organisation, like "can a customer also be a supplier?", or "if a product is sold with two different forms of packaging, are those the same product or different products?", or "if a plane flies from New York to Dubai via Frankfurt, is that one flight or two (or maybe even three)?". The answers to these questions establish definitions of the terminology used for entities (customers, products, flights, flight segments) and their relationships and attributes. | What makes a successful data model? | What makes a successful data model? | [
"What makes a successful data model?"
] | {
"text": [
"accurately reflect the possible state of the external world being modeled"
],
"answer_start": [
346
]
} |
gem-squad_v2-train-7585 | 572fa97e04bcaa1900d76b7b | Database | The first task of a database designer is to produce a conceptual data model that reflects the structure of the information to be held in the database. A common approach to this is to develop an entity-relationship model, often with the aid of drawing tools. Another popular approach is the Unified Modeling Language. A successful data model will accurately reflect the possible state of the external world being modeled: for example, if people can have more than one phone number, it will allow this information to be captured. Designing a good conceptual data model requires a good understanding of the application domain; it typically involves asking deep questions about the things of interest to an organisation, like "can a customer also be a supplier?", or "if a product is sold with two different forms of packaging, are those the same product or different products?", or "if a plane flies from New York to Dubai via Frankfurt, is that one flight or two (or maybe even three)?". The answers to these questions establish definitions of the terminology used for entities (customers, products, flights, flight segments) and their relationships and attributes. | What must one understand in order to create a successful data model? | What must one understand in order to create a successful data model? | [
"What must one understand in order to create a successful data model?"
] | {
"text": [
"the application domain"
],
"answer_start": [
600
]
} |
gem-squad_v2-train-7586 | 572fa97e04bcaa1900d76b7c | Database | The first task of a database designer is to produce a conceptual data model that reflects the structure of the information to be held in the database. A common approach to this is to develop an entity-relationship model, often with the aid of drawing tools. Another popular approach is the Unified Modeling Language. A successful data model will accurately reflect the possible state of the external world being modeled: for example, if people can have more than one phone number, it will allow this information to be captured. Designing a good conceptual data model requires a good understanding of the application domain; it typically involves asking deep questions about the things of interest to an organisation, like "can a customer also be a supplier?", or "if a product is sold with two different forms of packaging, are those the same product or different products?", or "if a plane flies from New York to Dubai via Frankfurt, is that one flight or two (or maybe even three)?". The answers to these questions establish definitions of the terminology used for entities (customers, products, flights, flight segments) and their relationships and attributes. | Asking questions about an organization's needs will help to create what? | Asking questions about an organization's needs will help to create what? | [
"Asking questions about an organization's needs will help to create what?"
] | {
"text": [
"definitions of the terminology used for entities"
],
"answer_start": [
1027
]
} |
gem-squad_v2-train-7587 | 5a8c870efd22b3001a8d8a18 | Database | The first task of a database designer is to produce a conceptual data model that reflects the structure of the information to be held in the database. A common approach to this is to develop an entity-relationship model, often with the aid of drawing tools. Another popular approach is the Unified Modeling Language. A successful data model will accurately reflect the possible state of the external world being modeled: for example, if people can have more than one phone number, it will allow this information to be captured. Designing a good conceptual data model requires a good understanding of the application domain; it typically involves asking deep questions about the things of interest to an organisation, like "can a customer also be a supplier?", or "if a product is sold with two different forms of packaging, are those the same product or different products?", or "if a plane flies from New York to Dubai via Frankfurt, is that one flight or two (or maybe even three)?". The answers to these questions establish definitions of the terminology used for entities (customers, products, flights, flight segments) and their relationships and attributes. | What does a conceptual data model never do? | What does a conceptual data model never do? | [
"What does a conceptual data model never do?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7588 | 5a8c870efd22b3001a8d8a19 | Database | The first task of a database designer is to produce a conceptual data model that reflects the structure of the information to be held in the database. A common approach to this is to develop an entity-relationship model, often with the aid of drawing tools. Another popular approach is the Unified Modeling Language. A successful data model will accurately reflect the possible state of the external world being modeled: for example, if people can have more than one phone number, it will allow this information to be captured. Designing a good conceptual data model requires a good understanding of the application domain; it typically involves asking deep questions about the things of interest to an organisation, like "can a customer also be a supplier?", or "if a product is sold with two different forms of packaging, are those the same product or different products?", or "if a plane flies from New York to Dubai via Frankfurt, is that one flight or two (or maybe even three)?". The answers to these questions establish definitions of the terminology used for entities (customers, products, flights, flight segments) and their relationships and attributes. | What data model is no longer a popular approach? | What data model is no longer a popular approach? | [
"What data model is no longer a popular approach?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7589 | 5a8c870efd22b3001a8d8a1a | Database | The first task of a database designer is to produce a conceptual data model that reflects the structure of the information to be held in the database. A common approach to this is to develop an entity-relationship model, often with the aid of drawing tools. Another popular approach is the Unified Modeling Language. A successful data model will accurately reflect the possible state of the external world being modeled: for example, if people can have more than one phone number, it will allow this information to be captured. Designing a good conceptual data model requires a good understanding of the application domain; it typically involves asking deep questions about the things of interest to an organisation, like "can a customer also be a supplier?", or "if a product is sold with two different forms of packaging, are those the same product or different products?", or "if a plane flies from New York to Dubai via Frankfurt, is that one flight or two (or maybe even three)?". The answers to these questions establish definitions of the terminology used for entities (customers, products, flights, flight segments) and their relationships and attributes. | What must one have no knowledge of in order to create a successful data model? | What must one have no knowledge of in order to create a successful data model? | [
"What must one have no knowledge of in order to create a successful data model?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7590 | 5a8c870efd22b3001a8d8a1b | Database | The first task of a database designer is to produce a conceptual data model that reflects the structure of the information to be held in the database. A common approach to this is to develop an entity-relationship model, often with the aid of drawing tools. Another popular approach is the Unified Modeling Language. A successful data model will accurately reflect the possible state of the external world being modeled: for example, if people can have more than one phone number, it will allow this information to be captured. Designing a good conceptual data model requires a good understanding of the application domain; it typically involves asking deep questions about the things of interest to an organisation, like "can a customer also be a supplier?", or "if a product is sold with two different forms of packaging, are those the same product or different products?", or "if a plane flies from New York to Dubai via Frankfurt, is that one flight or two (or maybe even three)?". The answers to these questions establish definitions of the terminology used for entities (customers, products, flights, flight segments) and their relationships and attributes. | Who is not allowed to produce a conceptual data model? | Who is not allowed to produce a conceptual data model? | [
"Who is not allowed to produce a conceptual data model?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7591 | 5a8c870efd22b3001a8d8a1c | Database | The first task of a database designer is to produce a conceptual data model that reflects the structure of the information to be held in the database. A common approach to this is to develop an entity-relationship model, often with the aid of drawing tools. Another popular approach is the Unified Modeling Language. A successful data model will accurately reflect the possible state of the external world being modeled: for example, if people can have more than one phone number, it will allow this information to be captured. Designing a good conceptual data model requires a good understanding of the application domain; it typically involves asking deep questions about the things of interest to an organisation, like "can a customer also be a supplier?", or "if a product is sold with two different forms of packaging, are those the same product or different products?", or "if a plane flies from New York to Dubai via Frankfurt, is that one flight or two (or maybe even three)?". The answers to these questions establish definitions of the terminology used for entities (customers, products, flights, flight segments) and their relationships and attributes. | What involves asking shallow questions to improve a data model? | What involves asking shallow questions to improve a data model? | [
"What involves asking shallow questions to improve a data model?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7592 | 572fabfe947a6a140053cb4e | Database | Having produced a conceptual data model that users are happy with, the next stage is to translate this into a schema that implements the relevant data structures within the database. This process is often called logical database design, and the output is a logical data model expressed in the form of a schema. Whereas the conceptual data model is (in theory at least) independent of the choice of database technology, the logical data model will be expressed in terms of a particular database model supported by the chosen DBMS. (The terms data model and database model are often used interchangeably, but in this article we use data model for the design of a specific database, and database model for the modelling notation used to express that design.) | In what form is the output of a logical database design? | In what form is the output of a logical database design? | [
"In what form is the output of a logical database design?"
] | {
"text": [
"schema"
],
"answer_start": [
303
]
} |
gem-squad_v2-train-7593 | 572fabfe947a6a140053cb4f | Database | Having produced a conceptual data model that users are happy with, the next stage is to translate this into a schema that implements the relevant data structures within the database. This process is often called logical database design, and the output is a logical data model expressed in the form of a schema. Whereas the conceptual data model is (in theory at least) independent of the choice of database technology, the logical data model will be expressed in terms of a particular database model supported by the chosen DBMS. (The terms data model and database model are often used interchangeably, but in this article we use data model for the design of a specific database, and database model for the modelling notation used to express that design.) | Which data model is displayed as a specific model that uses DBMS? | Which data model is displayed as a specific model that uses DBMS? | [
"Which data model is displayed as a specific model that uses DBMS?"
] | {
"text": [
"logical"
],
"answer_start": [
423
]
} |
gem-squad_v2-train-7594 | 572fabfe947a6a140053cb50 | Database | Having produced a conceptual data model that users are happy with, the next stage is to translate this into a schema that implements the relevant data structures within the database. This process is often called logical database design, and the output is a logical data model expressed in the form of a schema. Whereas the conceptual data model is (in theory at least) independent of the choice of database technology, the logical data model will be expressed in terms of a particular database model supported by the chosen DBMS. (The terms data model and database model are often used interchangeably, but in this article we use data model for the design of a specific database, and database model for the modelling notation used to express that design.) | A conceptual data model in separate from the choice of what? | A conceptual data model in separate from the choice of what? | [
"A conceptual data model in separate from the choice of what?"
] | {
"text": [
"database technology"
],
"answer_start": [
398
]
} |
gem-squad_v2-train-7595 | 5a8c8a11fd22b3001a8d8a5c | Database | Having produced a conceptual data model that users are happy with, the next stage is to translate this into a schema that implements the relevant data structures within the database. This process is often called logical database design, and the output is a logical data model expressed in the form of a schema. Whereas the conceptual data model is (in theory at least) independent of the choice of database technology, the logical data model will be expressed in terms of a particular database model supported by the chosen DBMS. (The terms data model and database model are often used interchangeably, but in this article we use data model for the design of a specific database, and database model for the modelling notation used to express that design.) | What form is the input of a logical database design? | What form is the input of a logical database design? | [
"What form is the input of a logical database design?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7596 | 5a8c8a11fd22b3001a8d8a5d | Database | Having produced a conceptual data model that users are happy with, the next stage is to translate this into a schema that implements the relevant data structures within the database. This process is often called logical database design, and the output is a logical data model expressed in the form of a schema. Whereas the conceptual data model is (in theory at least) independent of the choice of database technology, the logical data model will be expressed in terms of a particular database model supported by the chosen DBMS. (The terms data model and database model are often used interchangeably, but in this article we use data model for the design of a specific database, and database model for the modelling notation used to express that design.) | Which data model is displayed as a nonspecific model that uses DBMS? | Which data model is displayed as a nonspecific model that uses DBMS? | [
"Which data model is displayed as a nonspecific model that uses DBMS?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7597 | 5a8c8a11fd22b3001a8d8a5e | Database | Having produced a conceptual data model that users are happy with, the next stage is to translate this into a schema that implements the relevant data structures within the database. This process is often called logical database design, and the output is a logical data model expressed in the form of a schema. Whereas the conceptual data model is (in theory at least) independent of the choice of database technology, the logical data model will be expressed in terms of a particular database model supported by the chosen DBMS. (The terms data model and database model are often used interchangeably, but in this article we use data model for the design of a specific database, and database model for the modelling notation used to express that design.) | What is the conceptual data model dependent on? | What is the conceptual data model dependent on? | [
"What is the conceptual data model dependent on?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7598 | 5a8c8a11fd22b3001a8d8a5f | Database | Having produced a conceptual data model that users are happy with, the next stage is to translate this into a schema that implements the relevant data structures within the database. This process is often called logical database design, and the output is a logical data model expressed in the form of a schema. Whereas the conceptual data model is (in theory at least) independent of the choice of database technology, the logical data model will be expressed in terms of a particular database model supported by the chosen DBMS. (The terms data model and database model are often used interchangeably, but in this article we use data model for the design of a specific database, and database model for the modelling notation used to express that design.) | What terms are no longer used interchangeably? | What terms are no longer used interchangeably? | [
"What terms are no longer used interchangeably?"
] | {
"text": [],
"answer_start": []
} |
gem-squad_v2-train-7599 | 572facde04bcaa1900d76bd1 | Database | The final stage of database design is to make the decisions that affect performance, scalability, recovery, security, and the like. This is often called physical database design. A key goal during this stage is data independence, meaning that the decisions made for performance optimization purposes should be invisible to end-users and applications. Physical design is driven mainly by performance requirements, and requires a good knowledge of the expected workload and access patterns, and a deep understanding of the features offered by the chosen DBMS. | What decisions must be made in the last stage of database design? | What decisions must be made in the last stage of database design? | [
"What decisions must be made in the last stage of database design?"
] | {
"text": [
"performance, scalability, recovery, security"
],
"answer_start": [
72
]
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.