#36999: Reference to Ruby on Rails in Tutorial Part 2
-------------------------------------+-------------------------------------
Reporter: Sid R | Owner: (none)
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: 6.0
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by Sid R:
Old description:
> This is a minor nitpick, but I found the little blurb about the way Ruby
> on Rails a little confusing.
>
> The section in question is
> https://docs.djangoproject.com/en/6.0/intro/tutorial02/#creating-models
> and the text in question is:
>
> This includes the migrations - unlike in Ruby On Rails, for example,
> migrations are entirely derived from your models file, and are
> essentially a history that Django can roll through to update your
> database schema to match your current models."
>
> The 'unlike in Ruby on Rails' is not descriptive enough for a person not
> knowledgeable in Ruby on Rails to understand what the difference is, or
> why it might matter.
>
> I now wonder if it's simply unimportant, and not necessary to have in the
> documentation - i.e. just remove '{{{unlike in Ruby on Rails, for
> example}}}', and it's just as useful/helpful?
New description:
This is a minor nitpick, but I found the little blurb about the way Ruby
on Rails does migrations a little confusing.
The section in question is
https://docs.djangoproject.com/en/6.0/intro/tutorial02/#creating-models
and the text in question is:
This includes the migrations - unlike in Ruby On Rails, for example,
migrations are entirely derived from your models file, and are essentially
a history that Django can roll through to update your database schema to
match your current models."
The 'unlike in Ruby on Rails' is not descriptive enough for a person not
knowledgeable in Ruby on Rails to understand what the difference is, or
why it might matter.
I now wonder if it's simply unimportant, and not necessary to have in the
documentation - i.e. just remove '{{{unlike in Ruby on Rails, for
example}}}', and it's just as useful/helpful?
--
--
Ticket URL: <https://code.djangoproject.com/ticket/36999#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019d18c478cc-df670e1d-8fb1-4873-a651-6b0e7b96e4f8-000000%40eu-central-1.amazonses.com.
