tex: stylistical stuff
This commit is contained in:
parent
84b9f57ab9
commit
23c57658a5
12
tex/text.tex
12
tex/text.tex
@ -1400,8 +1400,8 @@ the table schema and relations entirely in Go.
|
|||||||
The best part about ent is that there is no need to define supplemental methods
|
The best part about ent is that there is no need to define supplemental methods
|
||||||
on the models, since with ent these are meant to be \emph{code generated} (in
|
on the models, since with ent these are meant to be \emph{code generated} (in
|
||||||
the older sense of word, not with Large Language Models). That creates files
|
the older sense of word, not with Large Language Models). That creates files
|
||||||
with models based on the types of the attributes in the database model and the
|
with models based on the types of the attributes in the database model, and the
|
||||||
respective relations are transformed into methods on the receiver and functions
|
respective relations are transformed into methods on the receiver or functions
|
||||||
taking object attributes as arguments.
|
taking object attributes as arguments.
|
||||||
|
|
||||||
For instance, if the model's attribute is a string value \texttt{Email}, ent
|
For instance, if the model's attribute is a string value \texttt{Email}, ent
|
||||||
@ -1415,14 +1415,14 @@ following:
|
|||||||
\item \texttt{EmailHasSuffix(suffix string)}
|
\item \texttt{EmailHasSuffix(suffix string)}
|
||||||
\end{itemize}
|
\end{itemize}
|
||||||
|
|
||||||
These methods can further be imported into other packages and makes working
|
These methods can further be imported into other packages and this makes
|
||||||
with the database a morning breeze.
|
working with the database a morning breeze.
|
||||||
|
|
||||||
|
|
||||||
\n{1}{Production}
|
\n{1}{Production}
|
||||||
|
|
||||||
It is, of course, recommended that the application runs in a secure
|
It is, of course, recommended that the application runs in a secure environment
|
||||||
environment although definitions of that almost certainly differ depending on
|
\allowbreak although definitions of that almost certainly differ depending on
|
||||||
who you ask. General recommendations would be either to effectively reserve a
|
who you ask. General recommendations would be either to effectively reserve a
|
||||||
machine for a single use case - running this program - so as to dramatically
|
machine for a single use case - running this program - so as to dramatically
|
||||||
decrease the potential attack surface of the host, or run the program isolated
|
decrease the potential attack surface of the host, or run the program isolated
|
||||||
|
Reference in New Issue
Block a user