Rdbi.PgSQL
0
0
Entering edit mode
@hrishikesh-deshmukh-1008
Last seen 9.7 years ago
Hi, My sincere apologies i have posted this question on BioC rather than R list. I want to install REmbeddedPostgres; it needs source, finding source is not a problem. I have a debian linux box, i had installed Postgres via apt-get; i have RdbiPgSQL installed so i have to get postgres-dev version. Now i want to use REmbeddedPostgres! which requires source, does installing source means another installation of postgres?! and i have to recreate DB's,load data etc! Which version of source should i get stable/developmental! Thanks, Hrishi --- Sean Davis <sdavis2@mail.nih.gov> wrote: > > On Mar 24, 2005, at 3:29 PM, Hrishikesh Deshmukh > wrote: > > > Hi All, > > > > library(RdbiPgSQL) > > > > #Connect to DB > > conn <- dbConnect(PgSQL(), host = "localhost", > dbname > > = "^^^^^",user="&&&&",password="#####") > > > > tt <- dbSendQuery(conn,"SELECT * FROM table WHERE > > signalrawintensity >= 200 and signalrawintensity > <= > > 20000 and pm_mm_other >=0") > > mytt <- dbGetResult(tt) > > > > This works fine but when i run: > > tt1 <- dbSendQuery(conn,"Create table trial as > SELECT > > * FROM all254gnxdt1 WHERE signalrawintensity >= > 200 > > and signalrawintensity <= 20000 and pm_mm_other > >=0") > > rd<-dbReadTable(conn,trial) > > > > I get this error: > > mylin <- dbGetResult(lin) > > You need to do: > > rd <- dbReadTable(conn,"trial") > > Note the quotes. > > The "did not produce any tuples" is a bit misleading > at times. I have > found that usually means that I messed up a command > (bad SQL, etc), so > it usually means go back to check your query. > > Hope that helps. > Sean > > __________________________________ Show us what our next emoticon should look like. Join the fun. http://www.advision.webevents.yahoo.com/emoticontest
GO GO • 687 views
ADD COMMENT

Login before adding your answer.

Traffic: 437 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6