CORE-5586#98
Conversation
| Max memory = !x | ||
| Elapsed time= !e sec', NULL, NULL, 'c_pg'); | ||
| Elapsed time = !e sec', NULL, NULL, 'c_pg'); | ||
| (1150, 'hvlad', '2006-02-03 19:17:10', 17, 45, 'Cpu = !u sec |
There was a problem hiding this comment.
No need to change history records :)
There was a problem hiding this comment.
I saw it there, so I played safe card. Should I remove this change?
There was a problem hiding this comment.
history2.sql contains old versions of changed messages. Formally, you should put pre-edited version of message as new record there, and never change existing records. But i really not sure it (history2.sql) is used somehow these days...
There was a problem hiding this comment.
I'd vote for deleting the history file. We have VCS logs anyway.
There was a problem hiding this comment.
I'd go further and delete more things not useful, as the fields for file and function name in messages2.sql. We have grep and others tools anyway.
There was a problem hiding this comment.
No objection fro my side, but this is offtop here ;)
There was a problem hiding this comment.
So. Should I revert the history2.sql for this PR or could it stay as it's going to be deleted anyway?
No description provided.