Earlier quoted context omitted.
A couple of years ago(2014) I made my first Python website and really enjoyed, however when it was time to put it onlin I quickly discovered that setting up hosting and configuring it was as large a task in getting to know pip, env, unicorn, apache2 and a plethora of other software to host it, is this still the case? Becaue this is what keeps me of hosting websites with python.
> A couple of years ago(2014) This is a niggle, but it one that has been niggling at me for the last few days. "A couple" means "two," not "several."
Django 3.2
191–195 of 195 posts
Re: Django 3.2
#192Earlier quoted context omitted.
Literally on https://www.dictionary.com/browse/couple , the page you linked: > idioms for couple a couple of, more than two, but not many, of; a small number of; a few: It will take a couple of days for the package to get there. A dinner party, whether for a couple of old friends or eight new acquaintances, takes nearly the same amount of effort. And some more dictionaries that agree: https://www.merriam-webster.com/…
The job of lexicographers is descriptive. They catalog all manner of inadvisable and illogical usages. Therefore the idea that a usage is correct because it appears in a dictionary is nonsensical, and your instruction to me to "look in a dictionary" shows that you do not understand what the basic function of one of these volumes is. A usage being common does not make it sensible or logical, and the use of "a couple"…
(and I didn't flag your original post, because I don't think merely being wrong justifies flagging)
Re: Django 3.2
#193Earlier quoted context omitted.
I have run into this exact problem. A many-to-many table had a business meaning, not just an "invisible" relationship. We wanted to put a model in front of it & add soft deletes and created-at/updated-at fields, at it was a mess of hoops and hacks to jump through.
Does this go easier in any other ORM/DBs that you might have used? Sounds like the semantics of the real-world stuff didn't quite match up to the DB semantics.
Actually writing the the tables was very freeing, no more separation and surprises in the translation between a single model and the multiple tables it can create.
For each new object, we wrote a SQLAlchemy Table object, a domain entity object, and optionally an adapter if you need to map field names between the two. The 300 lines of repo library code did the rest.
A little boilerplate, but no need for a ton of impenetrable, hyper-dynamic ORM code.
Alembic can autogenerate migrations from the SQLALchemy Table objects
Re: Django 3.2
#194Earlier quoted context omitted.
Maybe go look in a dictionary before you claim other people are illiterates
https://www.dictionary.com/browse/couple 1. two of the same sort considered together; pair. 2. two persons considered as joined together, as a married or engaged pair, lovers, or dance partners. Are we done here, or do you need another English lesson?
Re: Django 3.2
#195Earlier quoted context omitted.
The latest version of Tango with Django is from 2019 and is compatable with Danjango 2.2. Has a lot changed since then, if one was to work with 3.2?
My website was built in the 1.x version days and I don't think there have been any material breaking changes. My website is moderate in complexity... authentication, database, forms, file uploads, email, language support.