diff options
| author | eparreno <emili@eparreno.com> | 2010-04-08 16:45:53 +0200 |
|---|---|---|
| committer | eparreno <emili@eparreno.com> | 2010-04-08 16:45:53 +0200 |
| commit | 07b09bd404a39a9b2801d62fbce60416bba92ec8 (patch) | |
| tree | d09a6f894de17f0c7c44ef53a16644cea695dc41 /railties/guides/source/command_line.textile | |
| parent | e39950847c6f4a8e483f3dc44f50b6c0edc7b128 (diff) | |
| download | rails-07b09bd404a39a9b2801d62fbce60416bba92ec8.tar.gz rails-07b09bd404a39a9b2801d62fbce60416bba92ec8.tar.bz2 rails-07b09bd404a39a9b2801d62fbce60416bba92ec8.zip | |
CL guide: fix font format in rails plugin section
Diffstat (limited to 'railties/guides/source/command_line.textile')
| -rw-r--r-- | railties/guides/source/command_line.textile | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/railties/guides/source/command_line.textile b/railties/guides/source/command_line.textile index a8397a5b80..f2b53023a5 100644 --- a/railties/guides/source/command_line.textile +++ b/railties/guides/source/command_line.textile @@ -264,12 +264,12 @@ h4. +rails dbconsole+ h4. +rails plugin+ -The +rails plugin+ command simplifies plugin management; think a miniature version of the Gem utility. Let's walk through installing a plugin. You can call the sub-command *discover*, which sifts through repositories looking for plugins, or call *source* to add a specific repository of plugins, or you can specify the plugin location directly. +The +rails plugin+ command simplifies plugin management; think a miniature version of the Gem utility. Let's walk through installing a plugin. You can call the sub-command +discover+, which sifts through repositories looking for plugins, or call +source+ to add a specific repository of plugins, or you can specify the plugin location directly. -Let's say you're creating a website for a client who wants a small accounting system. Every event having to do with money must be logged, and must never be deleted. Wouldn't it be great if we could override the behavior of a model to never actually take its record out of the database, but *instead*, just set a field? +Let's say you're creating a website for a client who wants a small accounting system. Every event having to do with money must be logged, and must never be deleted. Wouldn't it be great if we could override the behavior of a model to never actually take its record out of the database, but instead, just set a field? + +There is such a thing! The plugin we're installing is called +acts_as_paranoid+, and it lets models implement a +deleted_at+ column that gets set when you call destroy. Later, when calling find, the plugin will tack on a database check to filter out "deleted" things. -There is such a thing! The plugin we're installing is called "acts_as_paranoid", and it lets models implement a "deleted_at" column that gets set when you call destroy. Later, when calling find, the plugin will tack on a database check to filter out "deleted" things. -================================================================================== <shell> $ rails plugin install http://svn.techno-weenie.net/projects/plugins/acts_as_paranoid + ./CHANGELOG |