hi,
recently we added a change in Ceilometer to lower the size of our id
fields in our storage model[1]. the reason we did this was because the
original size of varchar(255) we assigned to ids were so large that if
we wanted to generate some of our larger constraint requirements, it
would hit
On 06/26/2015 11:00 AM, gordon chung wrote:
hi,
recently we added a change in Ceilometer to lower the size of our id
fields in our storage model[1]. the reason we did this was because the
original size of varchar(255) we assigned to ids were so large that if
we wanted to generate some of our lar
On 26/06/2015 1:42 PM, Jay Pipes wrote:
On 06/26/2015 11:00 AM, gordon chung wrote:
hi,
recently we added a change in Ceilometer to lower the size of our id
fields in our storage model[1]. the reason we did this was because the
original size of varchar(255) we assigned to ids were so large th
On Fri, Jun 26, 2015 at 12:27 PM, gordon chung wrote:
>
>
> On 26/06/2015 1:42 PM, Jay Pipes wrote:
>
>> On 06/26/2015 11:00 AM, gordon chung wrote:
>>
>>> hi,
>>>
>>> recently we added a change in Ceilometer to lower the size of our id
>>> fields in our storage model[1]. the reason we did this w
I suppose it is redundant to point out the following, but hey, you know
without a bit of dogma each and every day on a mailing list how could
we call ourselves a real open source project? Apologies to people
for whom this is review.
An identifier which is derived from its context and contains
me
On 27/06/2015 4:29 AM, Chris Dent wrote:
Providing or displaying meaning is why we have other fields or
lookup by reference. An id and title are not the same thing.
The easiest way to follow the rules (that is to create unique,
universal, persistent, portable and meaningless identifiers) is to
