search for: coerceabl

...functions getTable(), assignTable(), existsTable(), and removeTable(). They all mimic the corresponding R/S get(), assign(), exists(), and remove(), and they all work with a connection object and an sql table name (NOT generic SQL queries); assignTable() assigns a data.frame object (or coerceable) to the database. (These functions provide the basis for "user-defined databases in S -- see below.) > How should I use resultSets ? I am not able to close neither a > connection nor a ResultSet. I tried with close(con). > Thanks for any help. I used the following script:...

...ing isTRUE] > > IM(H?)O, it would be best for both mean.default() and sd() to use > if(isTRUE(as.logical(na.rm))) -- this converts NULL, numeric(0), zero > numeric values, etc. to FALSE, non-zero numeric values (including > complex numbers not equal to 0+0i) to TRUE ... fails on un-coerceable > stuff like functions, environments ... > > > ?as.logical? attempts to coerce its argument to be of logical > type. In numeric and complex vectors, zeros are ?FALSE? and > non-zero values are ?TRUE?. For ?factor?s, this uses the ?levels? > (labels). Like...

Hi fantastic rails core developers. Speaking of version 2.3.5: I find it rather error_prone that values such that "some text" is silently converted to false when stored in a boolean DB field. Among other things it means that assign "some text" to boolean fields on a model will not generate any validation messages (it will silently be converted to false). I think it is like

Using slot() on object (or "@") and using a nonexistent slotname returns an error (see example code). R> setClass("foobar", representation=list(a="numeric")) [1] "foobar" R> foobar <- new("foobar", a=5) R> foobar at a [1] 5 R> foobar at b Error: no slot of name "b" for this object of class "foobar" The details