Naming - Is “a log” a single entry or a book of entries?
up vote
0
down vote
favorite
This comes up often enough that I want to have a consistent answer with a source. It seems that some programmers (and that is what I care about here, the programming context - not so much the English usage) think that "a log" is a complete record (like one book) of things that have happened and it contains several entries. These programmers would name a database table something like "ContentChangeLog" and call its rows "entries." They wouldn't typically use the term "logs" to describe anything.
There are other programmers who think that "a log" is a single entry inside a collection of logs. They would name a database table something like "ContentChangeLogs" and call its rows "logs."
Is there a non-opinion-based, consistent answer to this, with a source? Thank you.
logging
add a comment |
up vote
0
down vote
favorite
This comes up often enough that I want to have a consistent answer with a source. It seems that some programmers (and that is what I care about here, the programming context - not so much the English usage) think that "a log" is a complete record (like one book) of things that have happened and it contains several entries. These programmers would name a database table something like "ContentChangeLog" and call its rows "entries." They wouldn't typically use the term "logs" to describe anything.
There are other programmers who think that "a log" is a single entry inside a collection of logs. They would name a database table something like "ContentChangeLogs" and call its rows "logs."
Is there a non-opinion-based, consistent answer to this, with a source? Thank you.
logging
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
This comes up often enough that I want to have a consistent answer with a source. It seems that some programmers (and that is what I care about here, the programming context - not so much the English usage) think that "a log" is a complete record (like one book) of things that have happened and it contains several entries. These programmers would name a database table something like "ContentChangeLog" and call its rows "entries." They wouldn't typically use the term "logs" to describe anything.
There are other programmers who think that "a log" is a single entry inside a collection of logs. They would name a database table something like "ContentChangeLogs" and call its rows "logs."
Is there a non-opinion-based, consistent answer to this, with a source? Thank you.
logging
This comes up often enough that I want to have a consistent answer with a source. It seems that some programmers (and that is what I care about here, the programming context - not so much the English usage) think that "a log" is a complete record (like one book) of things that have happened and it contains several entries. These programmers would name a database table something like "ContentChangeLog" and call its rows "entries." They wouldn't typically use the term "logs" to describe anything.
There are other programmers who think that "a log" is a single entry inside a collection of logs. They would name a database table something like "ContentChangeLogs" and call its rows "logs."
Is there a non-opinion-based, consistent answer to this, with a source? Thank you.
logging
logging
asked Nov 19 at 18:10
Greg Smalter
3,93483258
3,93483258
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53380394%2fnaming-is-a-log-a-single-entry-or-a-book-of-entries%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown