Issue9

Title After loading two eSets, I can't load any more into the DB
Priority BUG Status resolved
Superseder Nosy List jgentry, sfalcon
Assigned To jgentry Topics

Created on 2006-03-27.15:11:00 by sfalcon, last changed 2006-05-31.20:50:26 by sfalcon.

Messages
msg90 (view) Author: sfalcon Date: 2006-05-31.20:50:26
I think this has been resolved.  Let's close the issue for now.
If something comes up, we'll reopen.
msg29 (view) Author: jgentry Date: 2006-03-29.14:45:30
I believe this is fixed as discussed in email (but put here to make it public).
 There was a call to substitute() in the R code to get the name of the eSet, but
I had put an as() call before that in case an exprSet was being passed in.  In
that case the substitute would return a blank name, so you likely were running
into having multiple datasets named "".  I submitted a fix, see if that helps
things.
msg10 (view) Author: sfalcon Date: 2006-03-27.15:11:00
I am seeing this:
> eset2pgsql(teuffel2004, db)
[1] "eSet  is already in the database"
NULL
>                                       

But it isn't there and this happens even when it is the first time
I have tried for a given eSet.?
History
Date User Action Args
2006-05-31 20:50:26sfalconsetstatus: testing -> resolved
messages: + msg90
2006-03-29 14:45:30jgentrysetstatus: unread -> testing
assignedto: jgentry
messages: + msg29
nosy: + jgentry
2006-03-27 15:11:00sfalconcreate