Re: [GENERAL] GUID for postgreSQL

2005-07-28 Thread Christopher Weimann 
On 07/28/2005-05:55AM, Stefan 'Kaishakunin' Schumacher wrote:
> 
> I was a little bit confused about the uniqueness of GUID (esp. using
> only 16 Bit [1]) and read the article about the UUID:
> http://en.wikipedia.org/wiki/Universally_Unique_Identifier
> 

16 BYTE not bit.  From the wiki...

   A UUID is essentially a 16-byte number and in its canonical form a UUID may 
look like this:

   550E8400-E29B-11D4-A716-44665544 


---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings

Re: [GENERAL] Wish: remove ancient constructs from Postgres

2006-02-27 Thread Christopher Weimann 
On 02/26/2006-10:36AM, Andrus Moor wrote:
> 
> It is difficult to write standard-compliant code in Postgres.
> There are a lot of constructs which have SQL equivalents but are still used
> widely, even in samples in docs!
> 
> For example, there are suggestions using
> 
> now()::CHAR!=foo
> 
> while the correct way is
> 
> CAST(CURRENT_DATE AS CHAR)<>foo
> 
> now() function, :: and != operators should be removed from language.
> 
> I like the Python logic: there is one way

Actually the python logic is

"There should be one-- and preferably only one --obvious way to do it."

Perhaps the suggestion should be to only use the SQL standard forms in
the documentation, making them the 'obvious' way.


---(end of broadcast)---
TIP 4: Have you searched our list archives?

   http://archives.postgresql.org