On 10 April 2013 20:16, Bruno Zerbo wrote:
> Hi guys,
> I tryed the hotfix/3.2.1 branch and the parse error relative of the cast
> operator was fixed!
> Thanks a lot.
> I think that yuo can closs the bug report.
Thanks for the confirmation.
The report has been closed [1] and I'll release 3.2.1 t
Hi guys,
I tryed the hotfix/3.2.1 branch and the parse error relative of the cast
operator was fixed!
Thanks a lot.
I think that yuo can closs the bug report.
Bye, Bruno
2013/4/8 Bruno Zerbo
> yes I'll try. But not today. Can you wait a couple of days?
>
>
> 2013/4/8 [email protected]
>
> Ok good
yes I'll try. But not today. Can you wait a couple of days?
2013/4/8 [email protected]
> Ok good, I take it you are on master branch. Could you please try the
> hotfix/3.2.1 branch ?
>
> > I use soci from git download of about 1 week ago
> >
> >
> > 2013/4/8 [email protected]
> >
> >> Hi Bruno
> >>
Ok good, I take it you are on master branch. Could you please try the
hotfix/3.2.1 branch ?
> I use soci from git download of about 1 week ago
>
>
> 2013/4/8 [email protected]
>
>> Hi Bruno
>>
>> What version of soci are you using ?
>>
>> It looks a bit like the Postgres regression that went into 3.
I use soci from git download of about 1 week ago
2013/4/8 [email protected]
> Hi Bruno
>
> What version of soci are you using ?
>
> It looks a bit like the Postgres regression that went into 3.2.0
>
> See commit c8ad2a884 for details. It should be fixed in 3.2.1.
>
> Poul
>
> > I tried with the es
Hi Bruno
What version of soci are you using ?
It looks a bit like the Postgres regression that went into 3.2.0
See commit c8ad2a884 for details. It should be fixed in 3.2.1.
Poul
> I tried with the escape beckslash \ (that is \:\:box3d) but the error was
> the same.
> Then I tried to change th
On 6 April 2013 16:55, Bruno Zerbo wrote:
> I tried with the escape beckslash \ (that is \:\:box3d) but the error was
> the same.
> Then I tried to change the cast syntax as suggested by Mateusz and the query
> worked.
Good. You've got workaround for the time being.
> Could be a good idea to ad
On 6 April 2013 14:31, Vadim Zeitlin wrote:
> On Sat, 6 Apr 2013 14:02:09 +0100 Mateusz Loskot wrote:
>
> ML> > the application gives my the following error:
> ML> >
> ML> > "Wt: fatal error: ERROR: syntax error at or near ""$1""
> ML> > LINE 1: ...etsrid('BOX3D(15.0118 37.4667, 15.2118 37,6667)'
I tried with the escape beckslash \ (that is \:\:box3d) but the error was
the same.
Then I tried to change the cast syntax as suggested by Mateusz and the
query worked.
Could be a good idea to add an escape strategy like that one of the
backslash (\) for parsing the colons.
Do I add the feature req
On Sat, 6 Apr 2013 14:02:09 +0100 Mateusz Loskot wrote:
ML> > the application gives my the following error:
ML> >
ML> > "Wt: fatal error: ERROR: syntax error at or near ""$1""
ML> > LINE 1: ...etsrid('BOX3D(15.0118 37.4667, 15.2118 37,6667)'::$1, 4326) ...
ML> >
ML> > the error is given in place
On 6 April 2013 10:27, Bruno Zerbo wrote:
> hi,
> I'm working with an app that makes some query to a postgres db.
> I tried the following query with pgadmin and it works while thought the c++
> code I have a runtime error.
> This is the code:
>
> using namespace soci;
> Edge edge;
> soci:
hi,
I'm working with an app that makes some query to a postgres db.
I tried the following query with pgadmin and it works while thought the c++
code I have a runtime error.
This is the code:
using namespace soci;
Edge edge;
soci::session sql(postgresql, "hostaddr=127.0.0.1 user=postgres
p
12 matches
Mail list logo