Using Database Constraints Wisely

A70410682bd132d5edf76b42189ebb45?s=47 Barun Singh
December 13, 2011
Programming
0
66

Using Database Constraints Wisely

A70410682bd132d5edf76b42189ebb45?s=128

Barun Singh

December 13, 2011
Tweet

More Decks by Barun Singh

See All by Barun Singh
A70410682bd132d5edf76b42189ebb45?s=48 barunio
1
180
A70410682bd132d5edf76b42189ebb45?s=48 barunio
2
120

Other Decks in Programming

See All in Programming
15934fa2aa7b2ce21f091e9b7cffa856?s=48 manfredsteyer
0
140
53850955f15249a1a9dc49df6113e400?s=48 line_developers
5
1.4k
0fa1c2ed2eb4a18ddec3dd70cb1f72db?s=48 likr
2
250
1fab9d01b25e99522f3dfd01e3d4cb51?s=48 soutaro
0
430
26afa82334d1037f0ba602272b950c90?s=48 kazuhitotakahashi
0
210
4cd9f68f08d2200de34043e4ce049d03?s=48 yagieng
4
430
271fad8d53cd1f12f2b4b6d38e3d7bd3?s=48 uzulla
1
170
Beb422437c1dfb5366f197919e41ac50?s=48 lilobase
1
480
Acd2f6f7498ea41881e161e191aa7c02?s=48 yattom
3
400
Fed4c6cfec7502b771e12f08f8d5ec6d?s=48 okajun35
0
570
4ab3fec3e82ddb19bcadd93ef909a443?s=48 syucream
0
960
Fc815be82d09a2e922d4000b65b9f83b?s=48 74th
1
420

Featured

See All Featured
B83d5b590577969ee79a5ad845411a7d?s=48 ammeep
654
54k
D09fad3e36ae6841f54820be0e907f7a?s=48 rocio
155
11k
B3d6434763caa0ef5dc4b792662c49f7?s=48 smashingmag
282
46k
Bfd6b681ec6e8c9bef82ff0521c364f7?s=48 kastner
54
1.9k
1f74b13f1e5c6c69cb5d7fbaabb1e2cb?s=48 sferik
609
54k
4394ceb8b277f35ee3da7030384efb5d?s=48 davidbonilla
69
3.5k
0bce06bd06ee7a2c4f5500f25dcf7f18?s=48 paulrobertlloyd
71
3.5k
Eb8975af8e49e19e3dd6b6b84a542e26?s=48 qrush
283
18k
3d4519fd34b76fb265fc0237f3792bd4?s=48 danielanewman
199
19k
B3d6434763caa0ef5dc4b792662c49f7?s=48 smashingmag
228
17k
D47656e20ff5e42f125fc5ea0fd636c6?s=48 tmm1
61
7.5k
A0517b08532aec8ab2aae3f65d40ad86?s=48 hannesfritz
27
900

Transcript

  1. Using database constraints wisely Barun Singh bsingh@wegowise.com Founder & CTO

  2. What is a database? A collection of data that you

    can read, write, and organize The software tools that let you do this

  3. What do we want from a database? It should be

    … •  Reliable •  Fast •  Secure •  …

  4. A relational database is not the same as a generic

    data store

  5. A relational database is not the same as a generic

    data store

  6. What do we want from a relational database? It should

    be … •  Reliable •  Fast •  Secure •  Sensible •  …

  7. Wait a minute… Is this Rails approved™ ?

  8. The Rails way says… •  You should be database agnostic

    •  Application layer is the only really important part

  9. The database is important

  10. But why? Because you make mistakes.

  11. What’s the worst that can happen? •  Feature doesn’t work

    •  Site goes down •  Irrecoverable data loss

  12. I write tests. Why bother with database constraints? I test

    my entire application flow through integration tests. Why write unit tests?

  13. I write tests. Why bother with database constraints? My application

    requires Javascript, and I have JS validations. Why bother with model-level validations?

  14. Your database has an interface.

  15. How? •  Simple constraints: [not null] •  Unique indices • 

    Foreign keys [foreigner gem]

  16. It’s not always that simple

  17. Polymorphism Imageable Picture Employee Product

  18. Polymorphism What does this reference?

  19. Polymorphism

  20. Polymorpheus

  21. A couple little snags… How can you make sure that

    one picture has only an employee_id or product_id but not both? (xor constraints are tough) And what if the polymorphic relationship has to be unique?

  22. Polymorpheus The gem takes care of all of this for

    you through a simple migration method

  23. Polymorpheus The gem takes care of all of this for

    you through a simple migration method

  24. Polymorpheus

  25. Polymorpheus Also provides a validation method, model level validations are

    still important

  26. You can keep your application logic clean and set up

    your database properly

  27. Questions? bsingh@wegowise.com