Re: [GENERAL] Postgres Team: Thank You All

2006-09-21 Thread Stijn Vanroye
Brian Maguire schreef: To all involved in this project, I justed wanted to let you know how impressed and pleased I have been with postgres over the past 5 years . The timeliness and quality of the releases are always robust and stable. Every release has a very nice mix of admin, performance,

Re: [GENERAL] select unique items in db

2006-09-13 Thread Stijn Vanroye
a schreef: "select unique id" - i found this line in google search but i want to make select * as unique select unique * is or select distinct pls point out how to select unique items from a list of million items Maybe select distinct from ... or select distinct on (field1,field2) from ...

Re: [GENERAL] select unique items in db

2006-09-14 Thread Stijn Vanroye
a schreef: this doesnt work SELECT DISTINCT on link *, rank(ts_vec, to_tsquery('default', $qtxt)) FROM feed_entry WHERE ts_vec @@ to_tsquery('default', $qtxt) ORDER BY rank(ts_vec, to_tsquery('default', $qtxt)) DESC LIMIT 5 OFFSET 0 can you tell me how to get the DISTINCT elements in LINK t

Re: [GENERAL] select unique items in db

2006-09-15 Thread Stijn Vanroye
a select query could very well decrease perormance, but I can't tell you in what order of magnitude. Regards, Stijn. Stijn Vanroye wrote: a schreef: this doesnt work SELECT DISTINCT on link *, rank(ts_vec, to_tsquery('default', $qtxt)) FROM feed_entry WHERE ts_vec

Re: [GENERAL] Unicode problem ???

2004-04-21 Thread Stijn Vanroye
't be more specific about these things since I don't remember exactly WHY these things are done, but I do know they help :-) This was all set-up and figured out by one of my colleagues a while ago. I was not excactly into the database itself, but restricted

Re: [GENERAL] Unicode problem ???

2004-04-21 Thread Stijn Vanroye
> Hi Stijn, Hy Alexander, > I tried adding "set client_encoding to 'LATIN1'" to the > Connect Settings of > psqlODBC. It didn't help. I still get the same weird > characters when I look > at the data using SQL explorer. Damn (pardon me). I realy hoped that would do the trick. > Could this be

Re: [GENERAL] Unicode problem ???

2004-04-22 Thread Stijn Vanroye
> > What I personally don't understand is: if all my databases > > are UNICODE, why do I have to set the Client encoding to latin1 > > to get a correct result? Karsten Hilbert wrote: > Because LATIN1 isn't just a subset of UNICODE. If the data > coming out of the database *is* UNICODE *and* your c

Re: [GENERAL] Unicode problem ???

2004-04-22 Thread Stijn Vanroye
> Am Donnerstag, 22. April 2004 09:48 schrieb Stijn Vanroye: > > Wouldn't it be better if I just set my client encoding to > UNICODE in stead > > of LATIN1? I suppose the UNICODE encoding set is understood > by windows (and > > delphi), since I write progs for a w

Re: [GENERAL] What is wrong here?

2004-04-22 Thread Stijn Vanroye
My guess is that the user has no (insert) rights on the table Customers. Try something like this for your table: GRANT [your options] ON TABLE Customers TO SomeCustomer; (or to everyone if that's easyer) where your options best includes SELECT and INSERT Regards, Stijn Vanroye

Re: [GENERAL] What is wrong here?

2004-04-22 Thread Stijn Vanroye
27;m wrong (I'm still more or less a newbie with PostGres), please speak up. Regards, Stijn Vanroye > -Original Message- > From: Tumurbaatar S. [mailto:[EMAIL PROTECTED] > Sent: donderdag 22 april 2004 12:32 > To: Stijn Vanroye > Subject: Re: [GENERAL] What is wrong here?

Re: [GENERAL] Question about inserts

2004-04-23 Thread Stijn Vanroye
l argument are not evaluated. [end quote] Isn't it possible to pass "NULL" to the query in stead of ''? eg. update table set datefield=NULL Regards, Stijn Vanroye > Is it possible to to the following > > I have tables which are updated via webpage (perl) with

Re: [GENERAL] Question about inserts

2004-04-23 Thread Stijn Vanroye
Bruno Wolff III wrote: > On Fri, Apr 23, 2004 at 13:07:43 +0200, > Stijn Vanroye <[EMAIL PROTECTED]> wrote: > > Maybe you can do something with this function: > > > > [quote from the postgres docs] > > 9.12.2. COALESCE > > COALESCE(value [, ...]) >

Re: [GENERAL] Cancel query based on a timeout

2004-05-13 Thread Stijn Vanroye
and thinking into it. So once again, thank you for the (much apreciated) help. Stijn Vanroye FAR Courier B.V. IT Department Weerterveld 61 6231NC Meerssen (The Netherlands) > -Original Message- > From: Carl E. McMillin [mailto:[EMAIL PROTECTED] > Sent: dinsdag 11 mei 2004 20:0

[GENERAL] Cancel query based on a timeout

2004-05-10 Thread Stijn Vanroye
(e.g. 30 sec.) Is there some way to send a command to the postgres sever to stop running the query? We're using Postgres 7.3.4 and the latest ODBC driver. Programming is done with Borland Delphi 7 Regards, Stijn Vanroye ---(end of broadcast)---

Re: [GENERAL] Cancel query based on a timeout

2004-05-10 Thread Stijn Vanroye
tarts running, I would like to be able to abort that running query. In pgAdmin III you have a 'stop' button when you are running a query (next to the little green 'start' arrow). I would like to be able to implement something similar in my application. Regards, Stijn Vanroye

Re: [GENERAL] PostgreSQL on CoLinux

2004-06-01 Thread Stijn Vanroye
e of the two were on any of my backups. So I'm afraid I can't be of more help than this. I hope that some of the more advanced linux users (or maybe collin again) can post a little more info on the subject. Kind regards, Stijn Vanroye -Original Message- From: Vitaly Belman [mail

Re: [GENERAL] Large table search question

2004-06-01 Thread Stijn Vanroye
sed! This while regualar analyzes where done, and the data never changes (no mutations). I don't seem to grasp the full meaning of the above. Am I better of using several single field indices, or do mulitcolumn indices offer an advantage? If so in which case? Just made me wander... Reg

Re: [GENERAL] Large table search question[Scanned]

2004-06-01 Thread Stijn Vanroye
w and that's it. Works relatively fast now anyway. Regards. Richard Huxton wrote: > Stijn Vanroye wrote: > > I don't want to but in, I just find this an interesting discussion > > and would like to add my 2 cents: > > > > I have read this in the manual: (PostgreSQ