Re: Tacoma Narrows bridge (was: MySQL v. PostgreSQL ...)

On 8/2/07, Ben Scott <[EMAIL PROTECTED]> wrote: > I've heard it claimed that, before the first Tacoma Narrows bridge > failed, aerodynamics had never been considered significant in bridge > design. If you look at the bridges of the time, I can believe that. > Most of them were simple truss/arch d

Re: [OT] Re: Tacoma Narrows bridge (was: MySQL v. PostgreSQL ...)

On 8/2/07, Ben Scott <[EMAIL PROTECTED]> wrote: > On 8/2/07, Thomas Charron <[EMAIL PROTECTED]> wrote: > > The bridge was running an early beta of Windows.. > > Now, now, let's be reasonable. > > It could have been a general release version of Windows. > > ;-) In the 1940's? :-) --

Re: Tacoma Narrows bridge (was: MySQL v. PostgreSQL ...)

On Thu, 2 Aug 2007 17:06:23 -0400 "Ben Scott" <[EMAIL PROTECTED]> wrote: > What may be more apropos to your point is the fact that, once the > oscillation was observed, the bridge was apparently kept in active, > public service. Exactly. Like Challenger kept on flying after burned O rings we

Re: [OT] Re: Tacoma Narrows bridge (was: MySQL v. PostgreSQL ...)

On 8/2/07, Thomas Charron <[EMAIL PROTECTED]> wrote: > The bridge was running an early beta of Windows.. Now, now, let's be reasonable. It could have been a general release version of Windows. ;-) -- Ben ___ gnhlug-discuss mailing list gnh

[OT] Re: Tacoma Narrows bridge (was: MySQL v. PostgreSQL ...)

On 8/2/07, Ben Scott <[EMAIL PROTECTED]> wrote: > I can see quite a few possibilities: You forgot one.. The bridge was running an early beta of Windows.. -- -- Thomas ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.

Re: Tacoma Narrows bridge (was: MySQL v. PostgreSQL ...)

On 8/2/07, Bill Sconce <[EMAIL PROTECTED]> wrote: > Amateurishness includes succumbing to the temptation to not think > through to consequences when reality offers new data. In the Tacoma > Narrows case: "However, the mass of the bridge was considered sufficient > to keep it structurally sound."[3

Re: Tacoma Narrows bridge (was: MySQL v. PostgreSQL ...)

On Tue, 31 Jul 2007 17:53:47 -0400 (EDT) Ric Werme <[EMAIL PROTECTED]> wrote: > In that particular case, it was more along the line of inadequate > wind tunnel and simulation time. (The slide rules of the day were > slow and inaccurate.) I completely agree. "Inadequate wind tunnel time" may sou

Re: MySQL v. PostgreSQL, continued, was: Microsoft Access - two questions

udimentary. The concept of inheritence is also relativly new. Sequences are non existant. Custom data types are impossible. O'Reilly tends to publish books on many things that are being adopted, but many of these features are currently being developed and 'aged'. Peoples concep

Re: MySQL v. PostgreSQL, continued, was: Microsoft Access - two questions

On Jul 31, 2007, at 13:17, Ben Scott wrote: > I'm gonna have to start putting a "Please read I think everybody reads at least part of your messages before replying - what do you mean, exactly? -Bill - Bill McGonigle, Owner Work: 603.448.4440 BFC Computing, LLC Home:

Re: Tacoma Narrows bridge (was: MySQL v. PostgreSQL ...)

On Wed, 1 Aug 2007 09:52:30 -0400 "Bill Ricker" <[EMAIL PROTECTED]> wrote: > This is so near Arcadia/Mt.Dessert/Bar Harbor and the lovely new > bridge (Stay-cabled like Boston's) at Verona Went over both in June and have gone by the new one several times while they were building it. The bridge n

Re: Tacoma Narrows bridge (was: MySQL v. PostgreSQL ...)

> The twin for the Tacoma Narrows bridge is not that far down the road, > in Deer Isle Maine. > What? How did I grow up in Maine and not know that? My HS Physics instructor is highly negligent in not mentioning that when he showed us Galloping Gerti

Re: MySQL v. PostgreSQL, continued, was: Microsoft Access - two questions

On Tue, 2007-07-31 at 13:54 -0400, Paul Lussier wrote: > "Ben Scott" <[EMAIL PROTECTED]> writes: > > > I'm gonna have to start putting a "Please read and consider my > > entire message before replying" notice at the top of all my posts... > > But that would eliminate much of the hilarity ensuing

OpenFoam (was Re: Tacoma Narrows bridge (was: MySQL v. PostgreSQL ...))

> > Someone explain to me again exactly how these bridges run Linux? :-P > > Perhaps there were computational fluid dynamics models of the bridges that > were run on Linux? ;) > And there is a very nice CFD package called "OpenFoam" that runs on Linux and is GPLed. It has come highly recom

Re: Tacoma Narrows bridge (was: MySQL v. PostgreSQL ...)

> One symptom which indicates that programmers are amateurs is that they > prematurely optimize. That's certainly true in compiler design, but > ... "More HP!" Oh - hp. I thought you were talking about printers. :-) > So real engineers laugh at the "10 more horsepower" crowd. Yes, but,

Re: Tacoma Narrows bridge (was: MySQL v. PostgreSQL ...)

On Tuesday 31 July 2007 04:33:04 pm Thomas Charron wrote: > On 7/31/07, Ray Cote <[EMAIL PROTECTED]> wrote: > > At 2:54 PM -0400 7/31/07, Jarod Wilson wrote: > > >On Tuesday 31 July 2007 01:14:40 pm Ben Scott wrote: > > > > The twin for the Tacoma Narrows bridge is not that far down the road, > > i

Re: Tacoma Narrows bridge (was: MySQL v. PostgreSQL ...)

On 7/31/07, Ray Cote <[EMAIL PROTECTED]> wrote: > At 2:54 PM -0400 7/31/07, Jarod Wilson wrote: > >On Tuesday 31 July 2007 01:14:40 pm Ben Scott wrote: > The twin for the Tacoma Narrows bridge is not that far down the road, > in Deer Isle Maine. >

Re: Tacoma Narrows bridge (was: MySQL v. PostgreSQL ...)

At 2:54 PM -0400 7/31/07, Jarod Wilson wrote: >On Tuesday 31 July 2007 01:14:40 pm Ben Scott wrote: >> On 7/31/07, Bill Sconce <[EMAIL PROTECTED]> wrote: >> > (Bridges give us some EXCELLENT examples of >> > what happens when an engineer goes a little bit amateur. You've probably >> > seen a v

Re: Tacoma Narrows bridge (was: MySQL v. PostgreSQL ...)

On Tuesday 31 July 2007 03:10:03 pm John Abreau wrote: > On Tue, July 31, 2007 2:54 pm, Jarod Wilson said: > > Ooh, ooh, everyone who's driven across the Tacoma Narrows bridge multiple > > times raise your hand! > > > > /me raises hand... > > Wow! You don't *look* that old, grampa! :-) Why would I

Re: Tacoma Narrows bridge (was: MySQL v. PostgreSQL ...)

On Tue, July 31, 2007 2:54 pm, Jarod Wilson said: > > Ooh, ooh, everyone who's driven across the Tacoma Narrows bridge multiple > times raise your hand! > > /me raises hand... > Wow! You don't *look* that old, grampa! :-) -- John Abreau / Executive Director, Boston Linux & Unix IM: [EMAIL PRO

Re: Tacoma Narrows bridge (was: MySQL v. PostgreSQL ...)

On Tuesday 31 July 2007 01:14:40 pm Ben Scott wrote: > On 7/31/07, Bill Sconce <[EMAIL PROTECTED]> wrote: > > (Bridges give us some EXCELLENT examples of > > what happens when an engineer goes a little bit amateur. You've probably > > seen a video of the Tacoma Narrows bridge coming apart.) > >

Re: MySQL v. PostgreSQL, continued, was: Microsoft Access - two questions

"Ben Scott" <[EMAIL PROTECTED]> writes: > I'm gonna have to start putting a "Please read and consider my > entire message before replying" notice at the top of all my posts... But that would eliminate much of the hilarity ensuing from those who take snippets of your posts completely out of conte

Re: MySQL v. PostgreSQL, continued, was: Microsoft Access - two questions

On 7/31/07, Jon 'maddog' Hall <[EMAIL PROTECTED]> wrote: > Oh well, they just added "stored procedures" in 5.0 On 7/31/07, Marc Nozell <[EMAIL PROTECTED]> wrote: > And a bunch of other useful features such as triggers, views and more > storage engines for specialized database needs (some via 3rd p

Tacoma Narrows bridge (was: MySQL v. PostgreSQL ...)

On 7/31/07, Bill Sconce <[EMAIL PROTECTED]> wrote: > (Bridges give us some EXCELLENT examples of > what happens when an engineer goes a little bit amateur. You've probably > seen a video of the Tacoma Narrows bridge coming apart.) In fairness to the engineers behind the Tacoma Narrows bridge, I

Re: MySQL v. PostgreSQL, continued, was: Microsoft Access - two questions

On Tue, Jul 31, 2007 at 11:53:23AM -0400, Jon 'maddog' Hall wrote: > > No annoyances like stored procedures > > Oh well, they just added "stored procedures" in 5.0 And a bunch of other useful features such as triggers, views and more storage engines for specialized database needs (some via 3rd pa

Re: MySQL v. PostgreSQL, continued, was: Microsoft Access - two questions

e bad ones leave such memorable disasters behind them! > > More fuel for the fire... Josh Berkus blogs, > > "What is does show is that PostgreSQL and MySQL are very, very close in > performance today and the outdated belief that MySQL is somehow multiple > times faste

Re: MySQL v. PostgreSQL, continued, was: Microsoft Access - two questions

> No annoyances like stored procedures Oh well, they just added "stored procedures" in 5.0 md ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

Re: MySQL v. PostgreSQL, continued, was: Microsoft Access - two questions

I've heard it said that MySQL is the ideal database for programmers who don't understand databases. No annoyances like stored procedures and server constraints to get in the way of your application code scribbling all over the tables. ;-) Of course, I gather MySQL has improved a fair bit in

Re: MySQL v. PostgreSQL, continued, was: Microsoft Access - two questions

emorable disasters behind them! > > More fuel for the fire... Josh Berkus blogs, > > "What is does show is that PostgreSQL and MySQL are very, very close in > performance today and the outdated belief that MySQL is somehow multiple > times faster than PostgreSQL is dramat

Re: MySQL v. PostgreSQL, continued, was: Microsoft Access - two questions

On 7/31/07, Ted Roche <[EMAIL PROTECTED]> wrote: > Josh Berkus blogs, > > "... should be picking a database based on which specific ... features, they > need in their database and not out of some ignorant assessment that > "Database X is way faster." Are you saying that decisions should be made

MySQL v. PostgreSQL, continued, was: Microsoft Access - two questions

he really, really good ones. Business application programmers follow the same normal curve as most everything else: few really, really good ones, few really, really bad ones, but the bad ones leave such memorable disasters behind them! More fuel for the fire... Josh Berkus blogs, "What is does show i

Re: Access to PostgreSQL conversion

--- David J Berube <[EMAIL PROTECTED]> wrote: > Hey all, > > While I'm thinking of Access and PostgreSQL, a quick > note. I recently > released one of my inhouse Access-to-PostgreSQL > conversion tools under > the GPL. Note, however, that Access and PostgreSQL

Access to PostgreSQL conversion

Hey all, While I'm thinking of Access and PostgreSQL, a quick note. I recently released one of my inhouse Access-to-PostgreSQL conversion tools under the GPL. Note, however, that Access and PostgreSQL have very different design methodologies, and a complex database will require reana

RE: postgresql

I fixed up the response to clear up what I wrote (Rich) and what the original msg was. Rich -Original Message- From: Sharpe, Richard Sent: Wednesday, June 11, 2003 11:24 AM To: 'Cole Tuininga'; Sharpe, Richard Cc: GNHLUG List Subject: RE: postgresql Cole See below for my

Re: FW: postgresql

>Don't look at me, I took the blue pill. ...well, then we'll all DEFINITELY be keeping our distance. ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss

Re: FW: postgresql

On Wed, 2003-06-11 at 11:42, Sharpe, Richard wrote: > Cole > > See below for my responses, hope it helps you out I certainly found it interesting - we may try playing with it. Thanks for taking time to answer the questions. -- Don't look at me, I took the blue pill. Cole Tuininga Lead Develo

FW: postgresql

-Original Message- From: Sharpe, Richard Sent: Wednesday, June 11, 2003 11:24 AM To: 'Cole Tuininga'; Sharpe, Richard Cc: GNHLUG List Subject: RE: postgresql Cole See below for my responses, hope it helps you out Rich Richard A Sharpe Database Analyst and Administr

RE: postgresql

-1072 EMAIL [EMAIL PROTECTED] / Webpage ...www.amherst1.com "Tenemos que tener fe" ("We must have faith") -Original Message- From: Cole Tuininga [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2003 1:57 PM To: Sharpe, Richard Cc: GNHLUG List Subject: RE: postgresql

Re: postgresql

Sharpe, Richard wrote: Erik I am a DBA and have been for over 20 years and my all time favorite RDBMS is DB2 and now especially that it runs on LINUX and that the LINUX flavor of DB2 is enjoying much attention from IBM, I think it is hands down better than Oracle. Thanks for your thought

RE: postgresql

I will answer but I am off to a meeting with people from the evil empire (M$). Rich -Original Message- From: Cole Tuininga [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2003 1:57 PM To: Sharpe, Richard Cc: GNHLUG List Subject: RE: postgresql On Tue, 2003-06-10 at 13:40, Sharpe

RE: postgresql

On Tue, 2003-06-10 at 13:40, Sharpe, Richard wrote: > Erik > > I am a DBA and have been for over 20 years and my all time favorite > RDBMS is DB2 and now especially that it runs on LINUX and that the LINUX > flavor of DB2 is enjoying much attention from IBM, I think it is hands down > better

Re: postgresql

On Tue, 2003-06-10 at 11:58, Erik Price wrote: > Cole Tuininga wrote: > > I don't have any comments except to say thanks for mentioning them Cole, > because I didn't know about any of these. So, just out of curiosity, > which database(s) do you prefer*? Truth be told, the only other one I ha

RE: postgresql

Price [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2003 11:58 AM To: Cole Tuininga Cc: [EMAIL PROTECTED] Subject: Re: postgresql Cole Tuininga wrote: > I agree that it has some great features, but when we looked into using > it, we found some serious drawbacks to it. If anybody has co

Re: postgresql

Cole Tuininga wrote: I agree that it has some great features, but when we looked into using it, we found some serious drawbacks to it. If anybody has comments on these, I'd be very interested to hear them. I don't have any comments except to say thanks for mentioning them Cole, because I didn'

postgresql

On Fri, 2003-06-06 at 15:03, Erik Price wrote: > * I have just started playing with Postgres (I used to use MySQL > exclusively) and I must say it is a really nice database, from the > application developer perspective. I agree that it has some great features, but when we looked into using it, w