|
|
|
|
LEADER |
00000cam a2200000 a 4500 |
001 |
OR_ocn123904793 |
003 |
OCoLC |
005 |
20231017213018.0 |
006 |
m o d |
007 |
cr unu|||||||| |
008 |
070501s2007 mau o 000 0 eng d |
040 |
|
|
|a UMI
|b eng
|e pn
|c UMI
|d OCLCQ
|d TXJ
|d CEF
|d OCLCQ
|d DEBSZ
|d OCLCQ
|d OCLCO
|d OCLCQ
|d CNNAI
|d OCLCF
|d OCLCQ
|d COO
|d OCLCQ
|d AU@
|d WYU
|d OCLCQ
|d UAB
|d CNCEN
|d OCLCQ
|d OCLCO
|d OCLCQ
|
020 |
|
|
|a 9780321502063
|
020 |
|
|
|a 032150206X
|
029 |
1 |
|
|a AU@
|b 000067101756
|
029 |
1 |
|
|a CHBIS
|b 006148814
|
029 |
1 |
|
|a CHVBK
|b 171144929
|
029 |
1 |
|
|a DEBSZ
|b 355404591
|
029 |
1 |
|
|a HEBIS
|b 291477380
|
035 |
|
|
|a (OCoLC)123904793
|
037 |
|
|
|a CL0500000009
|b Safari Books Online
|
050 |
|
4 |
|a QA76.9.D26
|b S33 2007
|
082 |
0 |
4 |
|a 005.74 S124 2007 [ONLINE]
|
049 |
|
|
|a UAMI
|
100 |
1 |
|
|a Sadalage, Pramod.
|
245 |
1 |
0 |
|a Recipes for continuous database integration :
|b Evolutionary database development /
|c by Pramod Sadalage.
|
260 |
|
|
|a Boston, Mass. :
|b Addison Wesley Professional,
|c 2007.
|
300 |
|
|
|a 1 online resource
|
336 |
|
|
|a text
|b txt
|2 rdacontent
|
337 |
|
|
|a computer
|b c
|2 rdamedia
|
338 |
|
|
|a online resource
|b cr
|2 rdacarrier
|
490 |
1 |
|
|a Short cut
|
500 |
|
|
|a "This short cut is a companion to the 2007 Jolt Productivity award winner, Refactoring databases: evolutionary database design by Scott W. Ambler and Pramod Sadalage, 0321293533, Addison-Wesley"--Cover
|
588 |
0 |
|
|a Print version record.
|
520 |
|
|
|a The past few years have seen the rise of agile or evolutionary methods in software development. These methods embrace change in requirements even late in the project. The ability to change software is because of certain practices that are followed within teams, such as Test Driven Development, Pair Programming, and Continuous Integration. Continuous Integration provides a way for software teams to integrate their work more than once a day, and promotes confidence in the software that is being developed by the team. It is thought that this practice is difficult to apply when continuously integrating the database with application code; hence, Evolutionary Database Development is considered a mismatch with agile methods. Pramod Sadalage shows that this is not necessarily true. Continuous Integration changed the way software is written. Why not extend and make the database part of the same Continuous Integration cycle so that you can see integrated results of your application as well as your database? Delivered in PDF format for quick and easy access, Recipes for Continuous Database Integration shows how the database can be brought under the preview of Continuous Integration, allowing all teams to integrate not only their application code, but also their database. This Short Cut presents a recipe for each task that needs to be done. Each recipe starts with a statement of a problem, followed by an explanation and solution. It provides concrete ways and examples to implement ideas in Refactoring Databases: Evolutionary Database Design by Scott W Ambler and Pramod Sadalage. Table of Contents What This Short Cut Covers Introduction Recipe 1 Continuously Integrating? Recipe 2 Extracting Your Database in Scripts Recipe 3 Using Version Control for Your Database Recipe 4 Automating Database or Schema Creation Recipe 5 Creating Objects in Your Database Recipe 6 Removing Database Objects Recipe 7 Removing Your Database Recipe 8 Using the Build Property Files Recipe 9 Re-Creating Your Application Database for Any Build Recipe 10 Making It Easy for New Developers to Join the Team Recipe 11 Integrating on Every Check-In Recipe 12 Naming Upgrade Scripts Recipe 13 Automating Database Change Script Creation Recipe 14 Implementing Database Version Checking Recipe 15 Sending Upgrades to Customers Sample Code Further Reading About ...
|
590 |
|
|
|a O'Reilly
|b O'Reilly Online Learning: Academic/Public Library Edition
|
650 |
|
0 |
|a Database design.
|
650 |
|
0 |
|a Computer software
|x Development.
|
650 |
|
0 |
|a Evolutionary programming (Computer science)
|
650 |
|
6 |
|a Bases de données
|x Conception.
|
650 |
|
6 |
|a Programmation évolutive.
|
650 |
|
7 |
|a Database design.
|2 blmlsh
|
650 |
|
7 |
|a Computer software
|x Development.
|2 blmlsh
|
650 |
|
7 |
|a Evolutionary programming (Computer science)
|2 blmlsh
|
650 |
|
7 |
|a Computer software
|x Development.
|2 fast
|0 (OCoLC)fst00872537
|
650 |
|
7 |
|a Database design.
|2 fast
|0 (OCoLC)fst00888032
|
650 |
|
7 |
|a Evolutionary programming (Computer science)
|2 fast
|0 (OCoLC)fst00917347
|
700 |
1 |
|
|a Ambler, Scott W.,
|d 1966-
|t Refractoring databases: evolutionary database design.
|
776 |
0 |
8 |
|i Print version:
|a Sadalage, Pramod.
|t Recipes for continuous database integration : evolutionary database development.
|d [Boston, Mass.] : Addison-Wesley Professional, ©2007
|z 9780321502063
|
830 |
|
0 |
|a Short cut.
|
856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9780321502063/?ar
|z Texto completo (Requiere registro previo con correo institucional)
|
994 |
|
|
|a 92
|b IZTAP
|