On 10/31/2008 12:57 PM, Corrado wrote:
On Friday 31 October 2008 16:29:13 you wrote:
See Prof. Ripley's message. RODBC is passing a buffer and buffer size
to the ODBC driver, and that driver is overflowing the buffer. You
could probably hide this bug by making the buffer larger, but the real
f
On Friday 31 October 2008 16:29:13 you wrote:
> See Prof. Ripley's message. RODBC is passing a buffer and buffer size
> to the ODBC driver, and that driver is overflowing the buffer. You
> could probably hide this bug by making the buffer larger, but the real
> fix is for the driver to take accou
On 10/31/2008 11:09 AM, Corrado wrote:
Dear friends,
the problem is on a postgresql 8.3.1 database on a 64 platform (the setting
described at the bottom of the previous email).
If the problems is with the odbc driver, why do the other applications connect
through odbc to the same databases w
Dear friends,
the problem is on a postgresql 8.3.1 database on a 64 platform (the setting
described at the bottom of the previous email).
If the problems is with the odbc driver, why do the other applications connect
through odbc to the same databases without any problem? I do not think it is
Prof Brian Ripley wrote:
> On Fri, 31 Oct 2008, Peter Dalgaard wrote:
>
>> Corrado wrote:
>>> I apologise The dsn is not empty, the database the dsn connects
>>> to is
>>> empty!
>>>
>>> You get the same error when connecting to a populated database.
>>
>> Do I? I wouldn't know...
>>
>> (You
On Fri, 31 Oct 2008, Peter Dalgaard wrote:
Corrado wrote:
I apologise The dsn is not empty, the database the dsn connects to is
empty!
You get the same error when connecting to a populated database.
Do I? I wouldn't know...
(You are _still_ not providing steps to reproduce the situatio
Corrado wrote:
> I apologise The dsn is not empty, the database the dsn connects to is
> empty!
>
> You get the same error when connecting to a populated database.
Do I? I wouldn't know...
(You are _still_ not providing steps to reproduce the situation!)
The actual maintainer might know,
I apologise The dsn is not empty, the database the dsn connects to is
empty!
You get the same error when connecting to a populated database.
Regards
On Friday 31 October 2008 12:26:39 Peter Dalgaard wrote:
> Corrado wrote:
> > Dear friends,
> >
> > there is a serious problem with RODBC o
Corrado wrote:
> Dear friends,
>
> there is a serious problem with RODBC on R from 2.6.2 to 2.8.0 on a
> postgresql
> 8.3 database.
>
> Let's say we define an empty dsn called "test", with user "postgres" and
> password "none". We test the connection with another application, and it
> works p
Dear friends,
there is a serious problem with RODBC on R from 2.6.2 to 2.8.0 on a postgresql
8.3 database.
Let's say we define an empty dsn called "test", with user "postgres" and
password "none". We test the connection with another application, and it
works properly.
When you call the databa
Hi,
Sweave for some reason does not respect encoding setting in pdf.options.
Everything is OK with ps.options. Thus when using non-default encoding
for graphs, resulting graphics eps file is correct, but pdf file is
not. Workaround is very simple, just use latex->dvips->ps2pdf chain to
get the in
This is
-- already fixed in R-patched early last week.
-- a duplicate of PR#13188.
You were explicitly asked not to report on already fixed or already
reported bugs -- see the FAQ. Note too that no one reported this during
the alpha/beta test period for 2.8.0, so responding to requests for
t
Full_Name: Andrew
Version: 2.8.0
OS: Linux-2.6.x
Submission from: (NULL) (78.107.248.171)
R-2.8.0 failes to build without X support due to a typo in the source code.
The following patch fixes this:
--- src/main/platform.c.orig2008-10-31 02:59:45.0 +0300
+++ src/main/platform.c 2008-1
2008/10/31 Duncan Murdoch <[EMAIL PROTECTED]>:
> On 10/30/2008 10:44 AM, Duncan Murdoch wrote:
>>
>> On 10/30/2008 10:15 AM, Martin Maechler wrote:
"FA" == Felix Andrews <[EMAIL PROTECTED]>
on Thu, 30 Oct 2008 17:40:17 +1100 writes:
>>>
>>>FA> Dear R-devel,
>>>
14 matches
Mail list logo