60.00
>rows=1000 width=36)
> -> Sort (cost=8.30..8.30 rows=10 width=28)
> -> Index Scan using pk_tblsidedruglink on tblsidedruglink
>(cost=0.00..8.14 rows=10 width=28)
>
> EXPLAIN
>
> On Thu, Feb 08, 2001 at 10:19:43AM -0600, Brice Ruth wrote:
> > FYI
ly selects.
-Brice
Stephan Szabo wrote:
>
> What does explain show for the query and have you run
> vacuum analyze recently on the tables?
>
> On Thu, 8 Feb 2001, Brice Ruth wrote:
>
> > The following query:
> >
> > SELECT
> >
rice
Stephan Szabo wrote:
>
> After you load the data, you need to run vacuum analzye. That'll
> get statistics on the current data in the table. Of course, I'm
> not sure that'll help in this case.
>
> On Thu, 8 Feb 2001, Brice Ruth wrote:
>
> > Stepha
rett W. McCoy" wrote:
>
> On Wed, 7 Feb 2001, Brice Ruth wrote:
>
> > Is there a simple (unix) command I can run on text files to convert
> > cr/lf to lf? The way I did it seemed pretty ass-backward to me (not to
> > mention time consuming).
>
> perl -pi -e
Is there a simple (unix) command I can run on text files to convert
cr/lf to lf? The way I did it seemed pretty ass-backward to me (not to
mention time consuming).
-Brice
Tom Lane wrote:
>
> Brice Ruth <[EMAIL PROTECTED]> writes:
> > Here's my latest tactic: I&#
ith this. I really
appreciate it tremendously.
-Brice
Tom Lane wrote:
>
> Brice Ruth <[EMAIL PROTECTED]> writes:
> > SELECT length(monographid) FROM tblpemdruglink WHERE drugid='DG-5039';
> > I get 5 returned to me, even though the string is only 4 ('2008&#
you all for the continued support on this.
Regards,
Brice Ruth
Michael Fork wrote:
>
> Run the following query:
>
> SELECT fdb.versionid, fdb.category, pem.drugid FROM tblfdbmono fdb,
> tblpemdruglink pem WHERE fdb.monographid = pem.monographid ORDER BY 1, 2,
> 3;
>
> i
That was my understanding as well, thank you for the clarification. :)
Tom Lane wrote:
>
> Brice Ruth <[EMAIL PROTECTED]> writes:
> > About the case-sensitivity, I was under the impression that PostgreSQL
> > was case-insensitive unless things were explicitly put
David,
About the case-sensitivity, I was under the impression that PostgreSQL
was case-insensitive unless things were explicitly put in quotes. This
is at least what I read in the book ...
-Brice
David Olbersen wrote:
>
> On Thu, 1 Feb 2001, Brice Ruth wrote:
>
> ->SELECT
linetext
+-+--
(0 rows)
And it takes about 3-4 seconds to return with that prognosis. What's
going on here?
-Brice
Peter Eisentraut wrote:
>
> Brice Ruth writes:
>
> > SELECT
> > a.Number,
> > a.Code,
> > a.T
l join' of these two tables returns the correct results ... and it
uses the same equality tests as the SQL join.
I'm more than happy to keep tryin' different things, though ... anything
to get to the bottom of this.
Regards,
Brice Ruth
"Ross J. Reedstrom" wrote:
>
> B
s to me that your delimited text file may have padded values,
> and "=" insists on exact matches for VARCHAR.
>
> update tblpemdruglink set monographid=btrim(monographid);
>
> might help, if the first query returns anything but 4.
>
> Ross
>
> On Tue, Feb
query or not. Please
advise.
Any help will be (as always) sincerely appreciated.
--
Brice Ruth
WebProjkt, Inc.
VP, Director of Internet Technology
http://www.webprojkt.com/
Ian,
Thanx - I figured the same about the ambiguity. I'll keep tryin' to
debug this with the vendor, then.
-Brice
Ian Harding wrote:
>
> Brice Ruth wrote:
>
> > Greetings.
> >
> > I'm working with a product provided by a third part that interface
not. Please
advise.
Any help will be (as always) sincerely appreciated.
--
Brice Ruth
WebProjkt, Inc.
VP, Director of Internet Technology
http://www.webprojkt.com/
15 matches
Mail list logo
