sergeynikitin wrote on Mon, 23 January 2017 09:46

Yes. I can. I've Add myself to this issue.

I really wonder what U++ revision you are using, because in trunk it is:

void PostgreSQLConnection::GetColumn(int i, Ref f) const
{
	if(PQgetisnull(result, fetched_row, i))
	{
		f = Null;
		return;
	}
	char *s = PQgetvalue(result, fetched_row, i);
	switch(info[i].type)
	{
		case INT64_V:
			f.SetValue(ScanInt64(s));
			break;
		case INT_V:
			f.SetValue(atoi(s));
			break;
		case DOUBLE_V:
			f.SetValue(atof(s));
			break;

and it is really really unlikely that this bug could get there in last 8 years, because in that period my major project is PGSQL and customers would really notice this within hours...

I have checked svn history and oldest revision available from 2009 has "atof" there...

Mirek