Re: [GENERAL] PostgreSQL 8.3.x Win32-Releases - always without psqlODBC?

2008-05-15 Thread gorsa
would like to know if there were developments on this. i also encountered this problem when i switched to 8.3 and also to 8.3.1 on my test server. my production server continues to be running ok on 8.1 though ; if there really is no more bundled odbc package with the postgres installer, i'd like to

Re: [GENERAL] PostgreSQL 8.3.x Win32-Releases - always without psqlODBC?

2008-05-16 Thread gorsa
thanks! my earlier installations had problems because stackbuilder could not connect thru my censornet proxy server. connecting my test server to a non-proxied internet connection solved the problem and i downloaded the needed softwares. richard -- Sent via pgsql-general mailing list (pgsql-gene

[GENERAL] maximum count of contiguous years

2009-09-03 Thread gorsa
is there a way to get the maximum count of contiguous years? for example: SELECT version(); PostgreSQL 8.3.1, compiled by Visual C++ 1400 CREATE TABLE sch_applform ( scholar_id integer NOT NULL, award_year numeric(4) NOT NULL, CONSTRAINT sch_applform_pkey PRIMARY KEY (scholar_id, award_year

Re: [GENERAL] maximum count of contiguous years

2009-09-04 Thread gorsa
thanks tim. will read up on rank() and pl/pgsql. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

[GENERAL] how to get unique identifier for a client

2008-10-10 Thread gorsa
hi all is there a way to get a unique identifier for a client? something like a machine id. session_user does not seem to work since a user can log on to many workstations. been through the list so i'm not searching for getting the ip address since the list said something like it's not supported in

Re: [GENERAL] how to get unique identifier for a client

2008-10-14 Thread gorsa
hi! unfortunately the unique identifier must not change from connection to connection, so that there can be a meaningful review of the usage table. is there a similar problem that you've encountered in the past that has this requirement? -- Sent via pgsql-general mailing list (pgsql-general@postg