[Django] #36999: Reference to Ruby on Rails in Tutorial Part 2

Django

unread,

Mar 22, 2026, 10:11:01 PMMar 22

to django-...@googlegroups.com

#36999: Reference to Ruby on Rails in Tutorial Part 2
-----------------------+------------------------------------------------
Reporter: Sid R | Type: Cleanup/optimization
Status: new | Component: Documentation
Version: 6.0 | Severity: Normal
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------+------------------------------------------------
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?
--
Ticket URL: <https://code.djangoproject.com/ticket/36999>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,

Mar 22, 2026, 11:37:08 PMMar 22

to django-...@googlegroups.com

#36999: Reference to Ruby on Rails in Tutorial Part 2

-------------------------------------+-------------------------------------
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

unread,

Mar 23, 2026, 1:58:22 AMMar 23

to django-...@googlegroups.com

#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
-------------------------------------+-------------------------------------

Comment (by Vidhi Singh):

I would like to work on this.
--
Ticket URL: <https://code.djangoproject.com/ticket/36999#comment:2>

Django

unread,

Mar 23, 2026, 1:58:42 AMMar 23

to django-...@googlegroups.com

#36999: Reference to Ruby on Rails in Tutorial Part 2
-------------------------------------+-------------------------------------

Reporter: Sid R | Owner: Vidhi
Type: | Singh
Cleanup/optimization | Status: assigned

Changes (by Vidhi Singh):

* owner: (none) => Vidhi Singh
* status: new => assigned

--
Ticket URL: <https://code.djangoproject.com/ticket/36999#comment:3>

Django

unread,

Mar 23, 2026, 3:49:20 AMMar 23

to django-...@googlegroups.com

#36999: Reference to Ruby on Rails in Tutorial Part 2
-------------------------------------+-------------------------------------

Reporter: Sid R | Owner: (none)
Type: | Status: new
Cleanup/optimization |

* owner: Vidhi Singh => (none)
* status: assigned => new

--
Ticket URL: <https://code.djangoproject.com/ticket/36999#comment:4>

Django

unread,

Mar 23, 2026, 11:16:32 AMMar 23

to django-...@googlegroups.com

#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
-------------------------------------+-------------------------------------

Comment (by sushmitayadav260723):

Hi, I would like to work on this issue. Is it available?
--
Ticket URL: <https://code.djangoproject.com/ticket/36999#comment:5>

Reply all

Reply to author

Forward