Tommy Pham wrote:
> On Wed, Mar 31, 2010 at 11:01 AM, Nathan Rixham wrote:
>> Tommy Pham wrote:
>>> On Wed, Mar 31, 2010 at 4:06 AM, Nathan Rixham wrote:
Tommy Pham wrote:
> As for spatial data types, I've never find much use for non scientific
> related. (example) If using point as
On Wed, Mar 31, 2010 at 11:16 AM, tedd wrote:
>
> I didn't say otherwise.
>
> At some point, you asked how others solve the unique problem and I provided
> my solution.
>
> Cheers,
>
> tedd
>
Sorry, I misread that.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://
On Wed, Mar 31, 2010 at 11:01 AM, Nathan Rixham wrote:
> Tommy Pham wrote:
>> On Wed, Mar 31, 2010 at 4:06 AM, Nathan Rixham wrote:
>>> Tommy Pham wrote:
As for spatial data types, I've never find much use for non scientific
related. (example) If using point as a PK, if MySQL stores it
At 11:08 AM -0700 3/31/10, Tommy Pham wrote:
On Wed, Mar 31, 2010 at 10:23 AM, tedd wrote:
At 5:56 PM -0700 3/30/10, Tommy Pham wrote:
On Tue, Mar 30, 2010 at 2:27 PM, Nathan Rixham wrote:
nope never been able to find any significant advantage; and thus ended
up using http uri's in m
On Wed, Mar 31, 2010 at 10:23 AM, tedd wrote:
> At 5:56 PM -0700 3/30/10, Tommy Pham wrote:
>>
>> On Tue, Mar 30, 2010 at 2:27 PM, Nathan Rixham wrote:
>>
>>> nope never been able to find any significant advantage; and thus ended
>>> up using http uri's in my own domain space(s) which are alway
Tommy Pham wrote:
> On Wed, Mar 31, 2010 at 4:06 AM, Nathan Rixham wrote:
>> Tommy Pham wrote:
>>> As for spatial data types, I've never find much use for non scientific
>>> related. (example) If using point as a PK, if MySQL stores it the
>>> same way as PostgreSQL which is 16 bytes, how is that
On Wed, Mar 31, 2010 at 4:06 AM, Nathan Rixham wrote:
> Tommy Pham wrote:
>>
>> As for spatial data types, I've never find much use for non scientific
>> related. (example) If using point as a PK, if MySQL stores it the
>> same way as PostgreSQL which is 16 bytes, how is that any different -
>> p
At 5:56 PM -0700 3/30/10, Tommy Pham wrote:
On Tue, Mar 30, 2010 at 2:27 PM, Nathan Rixham wrote:
nope never been able to find any significant advantage; and thus ended
up using http uri's in my own domain space(s) which are always
guaranteed to be unique as I'm issuing them. bonus is that
Tommy Pham wrote:
>
> As for spatial data types, I've never find much use for non scientific
> related. (example) If using point as a PK, if MySQL stores it the
> same way as PostgreSQL which is 16 bytes, how is that any different -
> performance wise - than using UUID and storing it as binary(16
On Wed, Mar 31, 2010 at 2:57 AM, Nathan Rixham wrote:
> Tommy Pham wrote:
>> On Tue, Mar 30, 2010 at 2:27 PM, Nathan Rixham wrote:
>>
>>> nope never been able to find any significant advantage; and thus ended
>>> up using http uri's in my own domain space(s) which are always
>>> guaranteed to be
Tommy Pham wrote:
> On Tue, Mar 30, 2010 at 2:27 PM, Nathan Rixham wrote:
>
>> nope never been able to find any significant advantage; and thus ended
>> up using http uri's in my own domain space(s) which are always
>> guaranteed to be unique as I'm issuing them. bonus is that they can be
>> dere
On Tue, Mar 30, 2010 at 2:27 PM, Nathan Rixham wrote:
> nope never been able to find any significant advantage; and thus ended
> up using http uri's in my own domain space(s) which are always
> guaranteed to be unique as I'm issuing them. bonus is that they can be
> dereferenced and server as bot
Tommy Pham wrote:
> Hi,
>
> I'm just wondering if anyone on this list using some type of
> UID/UUID/GUID in any of the DB? If so, what DBMS/RDBMS are you using
> and how many rows do you have for the table(s) using it? What data
> type are you using for that column?
nope never been able to find
13 matches
Mail list logo
