[Info-Ingres] patch notes

#1

Hi All,

In the old days we used to get release notes with a patch. Now when I
download a patch from esd.ingres.com I don't get patch notes offered.

Is there some special incantation I need to get the patch notes for a
specific patch?

Martin Bowes

#2

Hi Martin,

Under the FTP and HTTP buttons, there is a link called 'readme'. That's
where you can find the patch notes.

Plus, it should be part of the tar file that gets downloaded
(patch.html).

Is there a particular patch that is missing the patch notes?

Regards,

Steve

________________________________

From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of
Martin Bowes
Sent: Friday, April 24, 2009 7:42 AM
To: Ingres and related product discussion forum
Subject: [Info-Ingres] patch notes

Hi All,

In the old days we used to get release notes with a patch. Now when I
download a patch from esd.ingres.com I don't get patch notes offered.

Is there some special incantation I need to get the patch notes for a
specific patch?

Martin Bowes

#3

Hi Steve,

The readme link caused the 'Update Profile' window to appear. That was
unexpected!

But the patch.html was in the patch tar file as you have described.
Thanks for letting me know as I hadn't noticed that.

Marty

From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of
Steven Shuriff
Sent: 24 April 2009 13:42
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] patch notes

Hi Martin,

Under the FTP and HTTP buttons, there is a link called 'readme'. That's
where you can find the patch notes.

Plus, it should be part of the tar file that gets downloaded
(patch.html).

Is there a particular patch that is missing the patch notes?

Regards,

Steve

________________________________

From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of
Martin Bowes
Sent: Friday, April 24, 2009 7:42 AM
To: Ingres and related product discussion forum
Subject: [Info-Ingres] patch notes

Hi All,

In the old days we used to get release notes with a patch. Now when I
download a patch from esd.ingres.com I don't get patch notes offered.

Is there some special incantation I need to get the patch notes for a
specific patch?

Martin Bowes

#4

I like the patch notes being available separately for download - you can
read before trying to download the patch.

I'd almost always prefer text format because it is easy then to read on any
platform, windows, green screen etc. And makes it easy to search for bug
numbers and key phrases.

Paul

From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Martin
Bowes
Sent: Friday, 24 April 2009 11:37 PM
To: Ingres and related product discussion forum
Cc: Steven Shuriff
Subject: Re: [Info-Ingres] patch notes

Hi Steve,

The readme link caused the 'Update Profile' window to appear. That was
unexpected!

But the patch.html was in the patch tar file as you have described. Thanks
for letting me know as I hadn't noticed that.

Marty

From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Steven
Shuriff
Sent: 24 April 2009 13:42
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] patch notes

Hi Martin,

Under the FTP and HTTP buttons, there is a link called 'readme'. That's
where you can find the patch notes.

Plus, it should be part of the tar file that gets downloaded (patch.html).

Is there a particular patch that is missing the patch notes?

Regards,

Steve

_____

From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Martin
Bowes
Sent: Friday, April 24, 2009 7:42 AM
To: Ingres and related product discussion forum
Subject: [Info-Ingres] patch notes

Hi All,

In the old days we used to get release notes with a patch. Now when I
download a patch from esd.ingres.com I don't get patch notes offered.

Is there some special incantation I need to get the patch notes for a
specific patch?

Martin Bowes

#5

Paul White wrote:

Quote:

I'd almost always prefer text format because it is easy then to read on any
platform, windows, green screen etc. And makes it easy to search for bug
numbers and key phrases.

ASCII text: the universal file format.

Grossly, tragically underrated IMO.

--
Roy

UK Ingres User Association Conference 2009 will be on Tuesday June 9, 2009
Go to http://www.iua.org.uk/join to get on the mailing list.

#6

On Apr 25, 2009, at 7:56 AM, Roy Hann wrote:

Quote:

Paul White wrote:

I'd almost always prefer text format because it is easy then to
read on any
platform, windows, green screen etc. And makes it easy to search
for bug
numbers and key phrases.

ASCII text: the universal file format.

Grossly, tragically underrated IMO.

--
Roy

You are obviously a simpleton ... XML solves all problems.

(now retreating to my personal bunker)

#7

Michael Leo wrote:

Quote:

On Apr 25, 2009, at 7:56 AM, Roy Hann wrote:

Paul White wrote:

I'd almost always prefer text format because it is easy then to
read on any
platform, windows, green screen etc. And makes it easy to search
for bug
numbers and key phrases.

ASCII text: the universal file format.

Grossly, tragically underrated IMO.

You are obviously a simpleton ... XML solves all problems.

(now retreating to my personal bunker)

You can run...

--
Roy

UK Ingres User Association Conference 2009 will be on Tuesday June 9, 2009
Go to http://www.iua.org.uk/join to get on the mailing list.

#8

I find it very satisfying to see a seemingly simple question like 'Where are the patch notes?' dissolve into a major slug-fest between some of the heavy hitters in the group.

Ahhh. I'm getting an all-over tingly sorta feeling...

Marty

________________________________

From: info-ingres-bounces (AT) kettleriver...ting (DOT) com on behalf of Roy Hann
Sent: Sun 26/04/2009 11:13
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: Re: [Info-Ingres] patch notes

Michael Leo wrote:

Quote:

On Apr 25, 2009, at 7:56 AM, Roy Hann wrote:

Paul White wrote:

I'd almost always prefer text format because it is easy then to
read on any
platform, windows, green screen etc. And makes it easy to search
for bug
numbers and key phrases.

ASCII text: the universal file format.

Grossly, tragically underrated IMO.

You are obviously a simpleton ... XML solves all problems.

(now retreating to my personal bunker)

You can run...

--
Roy

UK Ingres User Association Conference 2009 will be on Tuesday June 9, 2009
Go to http://www.iua.org.uk/join to get on the mailing list.

_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://www.kettleriverconsulting.com...fo/info-ingres

#9

Quote:

ASCII text: the universal file format.

Grossly, tragically underrated IMO.

You are obviously a simpleton ... XML solves all problems.

(now retreating to my personal bunker)

# Useful unix command for those still living in the dark ages.
# Print bug description
sed -n '/Bug 102500/,/^$/p' patch.html

What bothers me is all the overhead that goes with XML just to say something
simple. Recently I had to write an interface to an external banking type
interface. The simplest call is to retrieve an account balance, the key is
"Account number", the function "Get Balance". The response is the balance -
around 16 characters and around 30 optional characters for status and error
message. After it was wrapped appropriately, the message to the external
provider was around 600 characters. The returned message was around 700
characters. Of course this is under https so we have the encryption
overhead as well. And, fancy that, one of the big issues is throughput and
response times.

#10

On Apr 26, 2009, at 11:22 PM, Paul White wrote:

Quote:

ASCII text: the universal file format.

Grossly, tragically underrated IMO.

You are obviously a simpleton ... XML solves all problems.

(now retreating to my personal bunker)

# Useful unix command for those still living in the dark ages.
# Print bug description
sed -n '/Bug 102500/,/^$/p' patch.html

What bothers me is all the overhead that goes with XML just to say
something
simple. Recently I had to write an interface to an external banking
type
interface. The simplest call is to retrieve an account balance, the
key is
"Account number", the function "Get Balance". The response is the
balance -
around 16 characters and around 30 optional characters for status
and error
message. After it was wrapped appropriately, the message to the
external
provider was around 600 characters. The returned message was around
700
characters. Of course this is under https so we have the encryption
overhead as well. And, fancy that, one of the big issues is
throughput and
response times.

Of course, this overhead is not because of the size of the packet, but
likely because of the encryption PLUS the goofy overhead of the twenty-
three
libraries needed to parse and create the XML crap.

XML is like SQL. Both try to solve legitimate problems incorrectly,
insufficiently, and bureaucratically.

Michael Leo
Director of Managed Services
Kettle River Consulting

MLeo (AT) KettleRiverConsulting (DOT) com
+1 612-859-2108 (cell)
+1 612-605-1978 (fax)