Re: [SQL] Aggregate query for multiple records

2004-08-27 Thread Troy
shouldn't take that long, I would think. You have indexes on wid and date? Troy > > Hello, I am new to the list, my apology if this question is beyond the > scope or charter of this list. > > My questions is: > What is the best method to perform an aggregate qu

Re: [SQL] once again, sorting with Unicode

2003-02-20 Thread Troy
CTION sample_encoding_func (text) RETURNS text AS 'sample_encoding_func.so' LANGUAGE 'C' WITH (iscachable,isstrict); You can create an index with: create index dummyindex on usertable using btree (sample_encoding_func(username) text_ops); Troy > > At 20:16 19.2.2003, Tr

Re: [SQL] once again, sorting with Unicode

2003-02-19 Thread Troy
You can generate indexes for your custom functions, though, which will speed things up. This is what I've done, successfully. Troy > > JBJ <[EMAIL PROTECTED]> writes: > > Furthermore I will have to be able to switch between is_IS and others to > > get the corr

Re: [SQL] [OT] Inventory systems (private)

2002-12-09 Thread Troy
. I.e. instead of using a text variable in each record, use a unique id which references an entry in an attributes table. This won't affect the speed of the system but it will save some space. Or if nothing else, it will be more elegant. Cheers, Troy > > Troy, Andy, > > you b

Re: [SQL] [OT] Inventory systems (private)

2002-12-03 Thread Troy
= 100 AND textkey IN ('Diameter', 'Weight', 'Color', 'Type'); and so on. The indexes are just a fast guess. You would need to look at the queries you generate and decide which indexes are needed. Cheers, Troy Troy KorjuslommiTkso

Re: [SQL] Character translation?

2002-09-09 Thread Troy
Would this work? select recid, title, firstname || chr(32) || lastname::char(50) as expert, rank from mytable where length(lastname) <= 50; Troy > > Hi, > > I have a view like this: > create view myview as > select recid, title, firstname || chr(32) || las

Re: [SQL] Diferent databases on same query...

2001-10-23 Thread Troy
ially if they get updated frequently. The workaround, for now, is to have a table just for the foreign keys for the different systems, and to query the shared database separately from within your programming environment. Troy > > > "Douglas Rafael da Silva" <[E