Re: foxpro, odbc, data types and unnecessary convertions

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: foxpro, odbc, data types and unnecessary convertions
Дата
Msg-id 6639.1235604524@sss.pgh.pa.us
обсуждение исходный текст
Ответ на foxpro, odbc, data types and unnecessary convertions  (Fernando Moreno <azazel.7@gmail.com>)
Список pgsql-general
Fernando Moreno <azazel.7@gmail.com> writes:
> For numbers, I have to convert them first to string and then remove
> the spaces, the code looks like this: sql_string = "some sql" +
> alltrim( str( some_number ) ) + " more sql"; I can combine alltrim and
> str in a third function but it's still tricky. A shorter and
> presumably better way to do the same is: sql_string = "some_column =
> ?foxpro_variable ". The problem with the last option is that, watching
> the pgsql log, values are sent this way: '12345'::float(8), so for
> every numeric value, no matter its type, I'm sending 12 characters
> more and the server is doing convertions that I don't need.

> Having a lot of foreign keys and other numeric data, I think this
> behaviour is not so good for network (remote and poor connection) and
> server performance. I'm almost decided to keep doing the trim/str
> thing, but my question is: am I exaggerating? what would you do?

You're obsessing over an issue that is almost certainly not going to
make a measurable difference.  You can probably improve your application
performance a lot more by expending the same effort somewhere else.

            regards, tom lane

В списке pgsql-general по дате отправления:

Предыдущее
От: "Roderick A. Anderson"
Дата:
Сообщение: Tangent Ref: Valid characters for user/role/group names?
Следующее
От: Craig Ringer
Дата:
Сообщение: Re: Can I use a query with UPDATE on its SET?