On Mon, Mar 25, 2002 at 03:01:54PM +0000, Oliver Elphick wrote: > On Mon, 2002-03-25 at 13:59, Carel Fellinger wrote: ... > > So the big question is: > > > > Does anyone know whether it's possible to bypass the SQL layer in > > PostgresSQL? > > No, it isn't possible.
Thanks for the confirmation:( ... > mysql may be a good choice, depending on what you want to do. For > simple lookups, without much updating, it may well be faster. mysql's > weakness appears to be in running multiple updating users, in the lack > of SQL features such as subselects, lower data security (because > transactions are optional extras) and poor conformance with SQL > standards especially the 'poor conformance' is really troublesome, so I think I'll go for PostgreSQL then. > But if you are ever going to need a real multi-user database, you might > as well go for PostgreSQL now. To speed things up, you could do > query-caching inside your application, though a simple indexed lookup is > pretty fast anyway. The caching is already done, and probably the performance isn't to big of a problem after all. You see, it's a late 80's program, and things have changed considerably in computer land since. I'm still shaking from the shock when my new computer (now 3 years old) appeared to be running 150 times faster then my old one:) -- groetjes, carel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
