Displaying 5 results from an estimated 5 matches for "sql_null_data".
2004 Jul 14
0
RODBC repeated rows problem
...ticed a previous note from Professor Ripley reporting that this problem
had been fixed with a version of RODBC from long ago. I am running RODBC
version 1.04, the latest version, however, so I'm at a loss as to what to
do.
One last note: I looked at the relevant line from sql.h that defines my
SQL_NULL_DATA, which RODBC (presumably) compares to its results. It says:
#define SQL_NULL_DATA (-1)
Unfortunately, I have no idea what this should mean to me :(
Are there any further diagnostics I can run? Any new versions of software I
should install? Any workarounds for the time being?
Thanks...
2010 Jan 03
24
SQLServer on Rails
Does any one know how to setup SQLserver with ruby1.9. It was working
on an earlier version and now nothing works! I have installed the
gems dbi ,dbd-odbc and activerecord-odbc-adapter and can connect in
straight Ruby. However, using rails with database.yml nothing works!
I hosed everything and reinstalled rails and now, I get Win32/Parite
virus on ruby.exe. Any ideas? I''m losing
2005 Jan 12
0
RODBC package -- sqlQuery(channel,.....,nullstring=0)stillgives NA's
...as to know
a solution to the select without coercing NAs to 0s after retrieving the
data
Best,
Luis
>>> Prof Brian Ripley <ripley at stats.ox.ac.uk> 12/01/2005 11:21:33 >>>
PLEASE do read the help page, which says
nullstring: character string to be used when reading 'SQL_NULL_DATA'
character items from the database.
^^^^^^^^^^^^^^^
so this does not apply to numeric items.
You can of course easily change numeric NAs to 0s, if you want to.
On Wed, 12 Jan 2005, Luis Rideau Cruz wrote:
> There is something strange in R behaviour (perhaps).
Your n...
2005 Jan 12
1
RODBC package -- sqlQuery(channel,.....,nullstring=0) stillgives NA's
There is something strange in R behaviour (perhaps).
I have run the same select in Oracle SQL*Plus (version 10.1.0.2.0) and
the output comes out with NULLs (which is what it ougth to be).
But in R I still get the same result with NAs (no matter I use
na.strings or nullstring arguments)
An output example follows below:
Using na.string="0" and nullstring="0" (sorry by the
2006 Oct 17
2
RODBC and NULL values
Dear All,
Writing sooner than I thought I'd need to.
I'm using R 2.4 on Mac OS X, with RODBC, PostgreSQL 8.1 and Actual's
ODBC driver. I have all my data in Filemaker 8.5, but it is
automatically exported into PostgreSQL for analysis as Filemaker's ODBC
and JDBC access is awful, slow and has a tendency to crash.
I have disability data where for each patient there is a survival