libpq API for PQcmdTuples()
| От | Mihai RUSU |
|---|---|
| Тема | libpq API for PQcmdTuples() |
| Дата | |
| Msg-id | Pine.LNX.4.58L0.0403012329570.15351@ahriman.bucharest.roedu.net обсуждение исходный текст |
| Ответы |
Re: libpq API for PQcmdTuples()
|
| Список | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi I was working recently on a mid-layer in my current projects for abstraction of SQL backends (curently for mysql and pgsql only) and found out that the libpq synonime of mysql_affected_rows is PQcmdTuples. However I really dont see why does it return char * ?? Is there any practical reason for this ? Curently I do (unsigned int)atoi(PQcmdTuples()) but I really dont feel very confortable with strings which might change their format at any time, not to mention the overhead to convert from str to int each time (and I dont expect to use this atoi rare heh). Thanks! - -- Mihai RUSU Email: dizzy@roedu.net GPG : http://dizzy.roedu.net/dizzy-gpg.txt WWW: http://dizzy.roedu.net "Linux is obsolete" -- AST -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAQ6ybPZzOzrZY/1QRAp8TAJ9DM2g0dsWtRGAhh7/lNRDssX/A9wCgn7Zd CXgCGtPx+Z8Fr+wIaQbPMC0= =m369 -----END PGP SIGNATURE-----
В списке pgsql-general по дате отправления: