World: r3wp

No problem, I'm usually much more productive under pressure ;-)

What's the current status of the postgresql driver   ?   Should one 
use mysql instead?

Or SQLite?

Not SQLite ... as I need something that is not memory based.

Got databases over 2Gb in size

SQLite is not memory based imo. It was RebDB. SQLite is the coolest 
thing on earth for the purpose it is supposed to serve :-) I mean 
- small, embeddable SQL engine. MySQLLib is not good solution imo, 
as it does not use SQL syntax and is not even free for embedded stuff.

There is one defficiency with SQLite - it is one user solution. Well, 
you can lock iirc, on file level (yes, even records), but SQL requests 
are not serialised, so you have to think twice, when more than one 
client would connect to database.

As for PostGress, IIRC the driver was in better state than the one 
of mySQL? It even used continual parsing. Doc said later on even 
mySQL driver will be rewritten that way, and maybe it already is, 
dunno.

Oh ... my bad.

I will have multiple clients accessing the database .. webserver, 
 update utiliities and main engine

Graham, Dock's Mysql driver run on eavy tasks without a hitch 8)

I'm just not sure that Mysql's license will eventually catch doc's 
work as well.

So, my preference is for postgresql if I can.

i have experienced a sort of problem : i needed a native driver for 
sql server in rebol because odbc wasnt suitable.  Does this exist 
or its not possible ?

I think sql server is only odbc

yes, what a pity.  i wonder how you can write a driver for a database 
.... i d like to try to do it just for fun

I've always wondered the same thing.  Same with creating ports of 
other language functions or custome controls (widgets) etc.

do you mean MS sql server?

Galt Barber wrote an SQL -Proxy for MS-SQL7 a few years ago. Modifying 
his script I was able to snoop the connections to the Caché DB too.

There is a native non-odbc client library for ms sql that is fast. 
There is also a TCP line protocol to access it.

can u tell me where is it ?

http://www.microsoft.com/downloads/details.aspx?FamilyId=DF0BA5AA-B4BD-4705-AA0A-B477BA72A9CB&DisplayLang=en#SNAC

That is the native client. Tell us if you have any luck with it.

By the way, ODBC and OLEDB are the native access methods of MS SQL 
Server - they are not an add-on layer. The tcp line protocol is the 
same protocol that the client libraries use. I think there is a few 
open source libraries that support the tcp connections (such as FreeTDS), 
though they may not be very current. You might be able to look at 
their code and docs to figure out the protocol.

my friend uses MSSQL with its command line tool ....

Even the command line tools connect through oledb or odbc.

ok i have the dll and i wonder what to do now .... if anyone can 
give me informations ....

If you have Command or the SDK write a wrapper using C Callbacks 
(google for that + rebol) and the /Library component

.

I am trying PGSQL with Doc's protocol and getting 'open pgsql'  error 
"** Script Error: find expected series argument of type: series object 
port bitse
t

** Near: fast-query: either args: find port/target"     This is Postgres 
9.0 recently downloaded.   Anyone having success with it?

Have you provided a database name in the connection URL?

Thanks Kaj.... looks like the NIC MAC is the only reliable one that 
meets the criteria.

ouch wrong group

Doc I tried db: open pgsql://postgres:[xxxxxxxx-:-127-:-0-:-0-:-1]:5432/postgres/ 
 where postgres is listed as a db on  pgAdmin III

Ouch it's the trailing slash

Btw, you only need to provide the port-id if it's not the default 
one (5432).

Let us know if it works ok with PostgreSQL v9.0. I haven't tested 
it since v7.3.

Will do.  Thanks for your work on this enabler ... it's a long list 
of your work that i leverage.  [looking for the donate button ....]

It's on the http://cheyenne-server.orgsite at the bottom ;-)

Doc,   PgSQL does not have same 'send-sql' and /flat options.   Is 
there a reason they can not parallel the mySQL use?

No particular reason, this driver wasn't much used by me or others, 
so I haven't work on it  as much as on the MySQL one. For SEND-SQL 
support with options, it should be quite easy to add IIRC (just a 
matter of copy/pasting some code from MySQL driver).

It looks like copy and paste but it had a warning on it   --- ;--- 
Internals (do not touch!)---   ..... which I took as "[this means 
you!]" .... I will give it a try in later today

Yes, there's a few  insertions to do on lower-level parts. I'll take 
a few minutes to do it after lunch. Btw, I don't have any pgsql server 
available, nor have time to setup one, so I'll let you test and eventually 
debug the new version. ;-)

Yes ... much better idea ...  I will do that testing while you polish 
off Red!

This is the new version to try: http://softinnov.org/tmp/pgsql-protocol-091.r

I am trying some of the code from mySQL and get a PgSQL error "** 
Script Error: Invalid argument: TABLE
** Where: forever
** Near: to integer! trim pos"

I hit this on an earlier install before today's fix ... I had atributed 
it to a problem with PgSQL version 8.4 install.

It comes on CREATE Table as well as SQL without table references 
in it ... e.g. simple SELECT

The error message seems to be the problem ... the table is CREATEd 
and is usable from new rebol sessions which load the protocol fresh.

Thanks Doc.  I can work around that TABLE message using the pgAdmin. 
 The Send-SQL and /FLAT protocol updates work exactly the same as 
on MySQL for me.

Glad to hear that.