On 06/14/2018 12:19 PM, Jeff Ortel wrote:
On 06/14/2018 10:37 AM, Daniel Alley wrote:
I will make one more suggestion. What about naming "id" -> "uuid"?
This carries the clear connotation that it is a unique identifier so
it is less likely to be confusing a la "id and _id", and is still
Thanks for your comment, Simon.
This introduces a perspective that is helpful to the discussion.
Filtering on an 'ID' natural key field (such as errata_ID) in a way that
is intuitive to the user is a significant use case.
On 06/14/2018 12:32 PM, Simon Baatz wrote:
My 2 cents (in my role as
On 06/14/2018 08:08 AM, Brian Bouterse wrote:
Jeff, can you elaborate more on your -1. I want to understand it. I'm
struggling to appreciate an "it's a convention" argument without
sources like an RFC or similar. I don't believe internet articles are
credible sources because any viewpoint can
>
> 1) If we do this, what happens when someone uses multiple plugins and both
> of them want to use id as well? Wouldn't it be better to have the core
> application reserving it and *all* plugins doing some derivative name?
>
One plugin wouldn't affect another since it's namespaced by table -
I've recently updated the plugin_template to work with the latest
master (3.0). [0] The template handles almost all of the bootstrapping
work necessary to write a new plugin, so it is valuable to keep it up to
date. Given human nature, it's likely that the plugin_template will tend
to fall behind
On Thu, Jun 14, 2018 at 10:28 AM, Dana Walker wrote:
> I'm -1 still but I had a few questions.
>
Why are you -1?
>
> 1) If we do this, what happens when someone uses multiple plugins and both
> of them want to use id as well? Wouldn't it be better to have the core
> application reserving it
I'm -1 still but I had a few questions.
1) If we do this, what happens when someone uses multiple plugins and both
of them want to use id as well? Wouldn't it be better to have the core
application reserving it and *all* plugins doing some derivative name?
2) I'd really like to hear more from
Jeff, can you elaborate more on your -1. I want to understand it. I'm
struggling to appreciate an "it's a convention" argument without sources
like an RFC or similar. I don't believe internet articles are credible
sources because any viewpoint can be validated by an internet post.
To recap my
