Re: SQLGetInfo Bug - Mailing list pgsql-odbc

From Dave Page
Subject Re: SQLGetInfo Bug
Date
Msg-id 03AF4E498C591348A42FC93DEA9661B8128E07@mail.vale-housing.co.uk
Whole thread Raw
In response to SQLGetInfo Bug  ("Dave Page" <dpage@vale-housing.co.uk>)
List pgsql-odbc

> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: 02 January 2003 15:03
> To: Dave Page
> Cc: pgsql-odbc@postgresql.org; Didier Moens
> Subject: Re: [ODBC] SQLGetInfo Bug
>
>
> "Dave Page" <dpage@vale-housing.co.uk> writes:
> > The garbage is not there if I use sprintf with a larger
> size of tmp.
> > I've tried variations of the code to check (without luck)
> but I assume
> > I'm not somehow knocking the null off the end of the string?
>
> You would be losing the trailing null if the snprintf is
> unable to fit its output into the buffer size it's told to
> use (at least, that's how most implementations of snprintf
> react, I think).
>
> It doesn't look like this should be enough data to overrun
> your buffer, but I don't have a better theory at the moment.
>
> Perhaps
>
>     snprintf(tmp, sizeof(tmp) - 1, "%s %s", ...);
>     tmp[sizeof(tmp) - 1] = '\0';
>
> would be better coding practice if you don't want to actually
> check snprintf's result.

Thanks Tom, that got it.

Regards, Dave.

pgsql-odbc by date:

Previous
From: Tom Lane
Date:
Subject: Re: SQLGetInfo Bug
Next
From: jaydip rathod
Date:
Subject: help