|
|
|
|
LEADER |
00000cam a2200000Ia 4500 |
001 |
OR_ocn826646985 |
003 |
OCoLC |
005 |
20231017213018.0 |
006 |
m o d |
007 |
cr unu|||||||| |
008 |
130204s2012 caua ob 001 0 eng d |
040 |
|
|
|a UMI
|b eng
|e pn
|c UMI
|d COO
|d DEBSZ
|d EBLCP
|d OCLCQ
|d FEM
|d OCLCQ
|d OCLCF
|d CEF
|d UAB
|d OCLCQ
|d OCLCO
|d OCLCQ
|d OCLCO
|
019 |
|
|
|a 968009790
|a 969009155
|
020 |
|
|
|a 1449357849
|
020 |
|
|
|a 9781449357849
|
020 |
|
|
|a 9781449357832
|
020 |
|
|
|a 1449357830
|
020 |
|
|
|a 9781449357801
|
020 |
|
|
|a 1449357806
|
020 |
|
|
|z 9781449357849
|
029 |
1 |
|
|a AU@
|b 000050590660
|
029 |
1 |
|
|a DEBBG
|b BV041121066
|
029 |
1 |
|
|a DEBSZ
|b 396759890
|
029 |
1 |
|
|a GBVCP
|b 785367926
|
029 |
1 |
|
|a AU@
|b 000067094924
|
035 |
|
|
|a (OCoLC)826646985
|z (OCoLC)968009790
|z (OCoLC)969009155
|
037 |
|
|
|a CL0500000187
|b Safari Books Online
|
050 |
|
4 |
|a QA76.9.D3
|b D374 2012
|
082 |
0 |
4 |
|a 005.7565
|
049 |
|
|
|a UAMI
|
100 |
1 |
|
|a Date, C. J.
|
245 |
1 |
0 |
|a View updating and relational theory /
|c C.J. Date.
|
260 |
|
|
|a Sebastopol, CA :
|b O'Reilly Media,
|c ©2012.
|
300 |
|
|
|a 1 online resource (1 volume) :
|b illustrations
|
336 |
|
|
|a text
|b txt
|2 rdacontent
|
337 |
|
|
|a computer
|b c
|2 rdamedia
|
338 |
|
|
|a online resource
|b cr
|2 rdacarrier
|
347 |
|
|
|a text file
|2 rda
|
588 |
0 |
|
|a Online resource; title from PDF title page (Safari, viewed Jan. 24, 2013).
|
504 |
|
|
|a Includes bibliographical references and index.
|
520 |
|
|
|a Views are virtual tables. That means they should be updatable, just as "real" or base tables are. In fact, view updatability isn't just desirable, it's crucial, for practical reasons as well as theoretical ones. But view updating has always been a controversial topic. Ever since the relational model first appeared, there has been widespread skepticism as to whether (in general) view updating is even possible. In stark contrast to this conventional wisdom, this book shows how views, just like base tables, can always be updated (so long as the updates don't violate any integrity constraints). More generally, it shows how updating always ought to work, regardless of whether the target is a base table or a view. The proposed scheme is 100% consistent with the relational model, but rather different from the way updating works in SQL products today. This book can: Help database products improve in the future Help with a "roll your own" implementation, absent such product improvements Make you aware of the crucial role of predicates and constraints Show you how relational products are really supposed to behave Anyone with a professional interest in the relational model, relational technology, or database systems in general can benefit from this book.
|
590 |
|
|
|a O'Reilly
|b O'Reilly Online Learning: Academic/Public Library Edition
|
650 |
|
0 |
|a Relational databases
|x Design and construction.
|
650 |
|
0 |
|a Database management.
|
650 |
|
6 |
|a Bases de données
|x Gestion.
|
650 |
1 |
7 |
|a Relational databases
|x Design and construction.
|2 bisacsh
|
650 |
|
7 |
|a Database management
|2 fast
|
856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9781449357832/?ar
|z Texto completo (Requiere registro previo con correo institucional)
|
938 |
|
|
|a ProQuest Ebook Central
|b EBLB
|n EBL1104863
|
994 |
|
|
|a 92
|b IZTAP
|