- Ruby on Rails Enterprise Application Development
- Table of Contents
- Ruby on Rails Enterprise Application Development
- Credits
- About the Authors
- Preface
- 1. Introduction
- 2. The Initial Problem
- 3. Laying the Foundations
- Supporting Rails Development
- Addressing the Challenges
- Setting Up a Rails Stack
- Installing a Custom Rails Stack
- Setting Up a Team Server
- Summary
- 4. Working with Rails
- The World According to Rails
- Setting Up a New Rails Application
- Connecting Rails to a Database
- ActiveRecord, Migrations, and Models
- The Scaffold
- Completing the Database
- Models in Detail
- Creating New Records in a Table via Models
- Finders
- Validation
- Testing
- Setting Up for Testing
- Anatomy of a Test Case
- What Should be Tested?
- Fixtures
- Tests for the Person Model
- A person should have a valid email address
- No two People can have the Same email address
- A person without a first name is invalid
- A person without a last name is invalid
- A person's gender must be set to 'M' or 'F'
- The full_name method should produce a correctly-formatted string
- The find_all_ordered method should correctly sort people
- Other Types of Assertion
- Becoming Driven by Testing
- Associations between Models
- Putting the Project into Context
- Summary
- 5. Building the User Interface
- 6. Into Production
- An Application Ready for Production
- The Application Server
- Setting up the Server
- Rory's Production Installation
- Errors in Production
- Back Up Rails
- Summary
- 7. Improving the User Experience
- Easy Access to the Application
- Users Need to be Able to Find Items Easily
- Adding AJAX to the Mix
- Show and Hide Company Address Using link_to_remote
- Help!
- Keep Talking to Users
- Summary
- 8. Extending the Application
- 9. Advanced Deployment
- Deployment with Capistrano
- Troubleshooting Deployment
- Housekeeping
- Optimizing a Rails Application
- Summary
- 10. Down the Track
- A. Running Your Own Gem Server
- Index
Having considered how he needs the contact data to be separated into tables and validated, his data structure consists of three tables as shown below.
After considering his validation options, he makes the following decisions.
First_nameandlast_nameshould not be empty.- Email should be a valid email address (matches regular expression) and unique to this person.
- Gender should be set to "M " or "F".
Address_idandcompany_idshould reference records in the appropriate tables.
- must have a
street_1entry - must have a valid
post_code(regular expression match) street_1+post_codemust be valid on creation of the address
A single regular expression is to be used to check and reformat telephone numbers.
Rory is now ready to start the practical steps of building his application.
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.