-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: update changelogs 4.3.0 #6971
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with either on the database errors.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BaseConnection::escape()
now excludes theRawSql
data type. This allows passing SQL strings into data.
This is potentially a really helpful feature, not sure if it deserves mention in highlights.
See `Forge`_. | ||
- To make the default configuration more secure, the default Validation Rules | ||
have been changed to **Strict Rules**. | ||
- The behavior when a database error occurs has been changed. See :ref:`exceptions-when-database-errors-occur`. | ||
|
||
BREAKING | ||
******** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Model:
Model::update()
method now raises aDatabaseException
if it generates an SQL
statement without a WHERE clause; Model does not support operations that update all records.
Line 99
Should be generates a SQL statement
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line 181 and 184 seem to have an unneeded empty line.
Line 183
- In addition to the added
$asQuery
parameter above the following methods also now return an array.
Should be:
- In addition to the added
$asQuery
parameter above the following methods also now returns an array.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems both a SQL
and an SQL
can be used.
https://english.stackexchange.com/questions/5265/an-sql-server-database-schema-or-a-sql-server-database-schema
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the following methods also now return an array
It seems return
is correct. Why returns
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I use an SQL
when referring to the language because it is an acronym of Structured Query Language and should be pronounced as S-Q-L. If referring to the driver Microsoft has, then it is a SQL
because it's pronounced as sequel.
return
is correct because it refers to the following methods
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just out of curiosity for you guys is it:
A SQLite database
Or
An SQLite database
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems to me that English native speakers pronounce "sequel".
In my country, SQL is a foreign word, and it is pronounced like "ess-queue-el" 100%.
It may surprise you but Microsoft SQL Server is pronounced like "ess-queue-el server".
SQLite is like "ess-queue-light".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I move between both of them so I'm fine with either solution. I don't think there's a right or wrong here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The official way to pronounce “MySQL” is “My Ess Que Ell” (not “my sequel”), but we do not mind if you pronounce it as “my sequel” or in some other localized way.
https://dev.mysql.com/doc/refman/8.0/en/what-is-mysql.html#idm139761506951328
I guess I've been saying it wrong all these years.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SQLite creator says pronounce it however you like.
https://english.stackexchange.com/questions/431329/what-is-the-correct-pronunciation-of-sqlite
Just reading that description, I can't see where it can be used. |
Description
Checklist: