Nice Quote from Celko

"Developers are more likely to port SQL Server to Postgres because it is
open source, supports more ANSI features, runs on more platforms, uses a
different ACID model and has a great optimizer. "

http://www.sqlservercentral.com/articles/Stairway+Series/89991/

--
Regards,
Richard Broersma Jr.

On 23/09/12 03:31, Richard Broersma wrote:
>
> "Developers are more likely to port SQL Server to Postgres because it
> is open source, supports more ANSI features, runs on more platforms,
> uses a different ACID model and has a great optimizer. "
>
> http://www.sqlservercentral.com/articles/Stairway+Series/89991/
>
> --
> Regards,
> Richard Broersma Jr.
It wanted me to login to read it.

Can you quote it more fully?

Cheers,.
Gavin

On Sat, Sep 22, 2012 at 1:54 PM, Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz
> wrote:

>
> http://www.sqlservercentral.com/articles/Stairway+Series/89991/
>>
>> --
>> Regards,
>> Richard Broersma Jr.
>>
>
> Can you quote it more fully?
>

Here is the excerpt that the quote comes from:

"Bottom Line

Porting applications to SQL Server is not the usual direction. Developers
are more likely to port SQL Server to Postgres because it is open source,
supports more ANSI features, runs on more platforms, uses a different ACID
model and has a great optimizer.

If you live in a Microsoft world and need to move Postgres code to SQL
Server, don’t expect the port to be easy. You might luck up, but that’s not
the way the smart money bets. The pure SQL part will not hard if the
original Postgres is clean and simple; you will have to write the extra
ANSI features with complicated T-SQL. The hard part is that Postgres
assumes a non-Microsoft environment and a different concurrency model."

--
Regards,
Richard Broersma Jr.

On Saturday, September 22, 2012 01:54:08 pm Gavin Flower wrote:
> On 23/09/12 03:31, Richard Broersma wrote:
> >
> > "Developers are more likely to port SQL Server to Postgres because it
> > is open source, supports more ANSI features, runs on more platforms,
> > uses a different ACID model and has a great optimizer. "
> >
> > http://www.sqlservercentral.com/articles/Stairway+Series/89991/
> >
> It wanted me to login to read it.

Read it using elinks, that's what I did.

Robert

Richard Broersma, 24.09.2012 01:09:
> Here is the excerpt that the quote comes from:
>
> "Bottom Line
>
> Porting applications to SQL Server is not the usual direction.
> Developers are more likely to port SQL Server to Postgres because it
> is open source, supports more ANSI features, runs on more platforms,
> uses a different ACID model and has a great optimizer.
>
> If you live in a Microsoft world and need to move Postgres code to
> SQL Server, don’t expect the port to be easy. You might luck up, but
> that’s not the way the smart money bets. The pure SQL part will not
> hard if the original Postgres is clean and simple; you will have to
> write the extra ANSI features with complicated T-SQL. The hard part
> is that Postgres assumes a non-Microsoft environment and a different
> concurrency model."

There are some similar posts out there:

http://facility9.com/2011/12/ten-reasons-postgresql-is-better-than-sql-server/
http://datachomp.com/archives/im-leaving-sql-server-for-postgres/

On 25/09/12 03:31, Robert Bernier wrote:
> On Saturday, September 22, 2012 01:54:08 pm Gavin Flower wrote:
>> On 23/09/12 03:31, Richard Broersma wrote:
>>> "Developers are more likely to port SQL Server to Postgres because it
>>> is open source, supports more ANSI features, runs on more platforms,
>>> uses a different ACID model and has a great optimizer. "
>>>
>>> http://www.sqlservercentral.com/articles/Stairway+Series/89991/
>>>
>> It wanted me to login to read it.
>
> Read it using elinks, that's what I did.
>
>
> Robert
Thanks

I have not checked everything, but noted that..

It claims
"[...]
The model for temporary tables is weaker than T-SQL in some ways. ...
You cannot create a temp table with column declarations, but only with a
query..
[...]"

this obviously false:
*
CREATE TEMP TABLE tem_tab
(
id SERIAL PRIMARY KEY,
payload text
);

INSERT INTO tem_tab (payload)
VALUES
('first'),
('second'),
('third'),
('fourth'),
('fifth'),
('sixth'),
('seventh'),
('eighth');

SELECT * FROM tem_tab ORDER BY payload;*

works in PostgreSQL

Gavin Flower, 24.09.2012 22:07:
> I have not checked everything, but noted that..
>
> It claims
> "[...]
> The model for temporary tables is weaker than T-SQL in some ways.
> You cannot create a temp table with column declarations, but only
> with a query
>
> this obviously false:

There is another wrong statement I noticed:

Other Data Types

Postgres also supports the BOOLEAN data type, which has the following characteristics:

* Does not support NULL values.

That of course is also not true.