[#1263] Draft of the updated Ruby FAQ — Dave Thomas <Dave@...>

33 messages 2000/02/08

[#1376] Re: Scripting versus programming — Andrew Hunt <andy@...>

Conrad writes:

13 messages 2000/02/15

[#1508] Ruby/GTK and the mainloop — Ian Main <imain@...>

17 messages 2000/02/19
[#1544] Re: Ruby/GTK and the mainloop — Yasushi Shoji <yashi@...> 2000/02/23

Hello Ian,

[#1550] Re: Ruby/GTK and the mainloop — Ian Main <imain@...> 2000/02/23

On Wed, Feb 23, 2000 at 02:56:10AM -0500, Yasushi Shoji wrote:

[#1516] Ruby: PLEASE use comp.lang.misc for all Ruby programming/technical questions/discussions!!!! — "Conrad Schneiker" <schneiker@...>

((FYI: This was sent to the Ruby mail list.))

10 messages 2000/02/19

[#1569] Re: Ruby: constructors, new and initialise — Yukihiro Matsumoto <matz@...>

The following message is a courtesy copy of an article

12 messages 2000/02/25

[ruby-talk:01577] Re: postgres

From: matz@... (Yukihiro Matsumoto)
Date: 2000-02-25 08:59:31 UTC
List: ruby-talk #1577
Hi,

In message "[ruby-talk:01576] postgres"
    on 00/02/25, ts <decoux@moulon.inra.fr> writes:

| Apparently all errors in postgres are fatal, it's normal ?
| In this example 'aa' is an invalid column name.

PGError is (wrongly) subclass of Exception.  Please specify PGError
explicitly in rescue clause, e.g.

  begin
    conn = PGconn.connect("", -1, "", "", "microsat", $USER, $PASS)
    print "HERE #{conn}\n"
    result = conn.exec("select aa from donnees")
  rescue PGError
    print "ERROR\n"
  ensure
    conn.close;
  end

It should be subclass of StandardError, in fact I fixed it locally,
and forgot to release.  X-<

I'll release Ruby/Postgres-0.5.4 real soon.

							matz.
p.s.
And new Ruby/Postgres maintainer is wanted.

In This Thread

Prev Next