Please try again. The problem should be fixed.
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to th
Thank you so much! It means a lot to me :-)
Cheers,
Rahul
On Friday, September 28, 2018 at 11:28:44 AM UTC+5:30, Massimo Di Pierro
wrote:
>
> Congratulations!
>
> On Monday, 17 September 2018 23:39:50 UTC-7, Rahul wrote:
>>
>> Hi Everyone,
>> I am glad to say that my application (
Congratulations!
On Monday, 17 September 2018 23:39:50 UTC-7, Rahul wrote:
>
> Hi Everyone,
> I am glad to say that my application (
> http://www.targetsoft.co.in/ ) is up and running on personal VPS. I've
> added links to total of three applications all written in web2py
>
> 1. HMS (
Hi Everyone,
I am glad to say that my application
(http://www.targetsoft.co.in/ ) is up and running on personal VPS. I've
added links to total of three applications all written in web2py
1. HMS (Hospital Management system ) coded back in 2016 - may have a few
issues
2. Target+ (Tic
Hi Anthony,
Yes there are many queries that are being fired - Since it is a
dashboard I have multiple queries being fired sequentially/simultaneously.
I have a number of those queries in try catch block as well. I certainly
agree that rolling back is not a good solution and in-fact I am in
On Wednesday, August 1, 2018 at 8:48:54 AM UTC-4, Rahul wrote:
>
> Hi Anthony,
> I used *db.rollback**()* and viola - A lot of my failing stuff
> started to work. I am rectifying the failing queries and still trying to
> figure out the incorrect SQL statement that is causing the error. F
Hi Anthony,
I used *db.rollback**()* and viola - A lot of my failing stuff
started to work. I am rectifying the failing queries and still trying to
figure out the incorrect SQL statement that is causing the error. For below
question - Again if I print db.rollback() a *None* is returned.
It sounds like this error can happen when you run an incorrect SQL
statement within a transaction and then follow with another statement. Is
it possible there is some earlier query you are running (maybe in one of
your model files) that does not work in Postgres? What happens if you call
db.rol
Basically, I am trying to compare *between *dates here. One other query
works but the ones specified earlier (below) do not. I am sure that there
is some programming mistake from my side. But I am not sure what it is -
Tickets = db((db.issues.date_today >= daysix) & (db.issues.date_today <=
to
Hi Anthony,
I am printing this to console - The query is trying to fetch
records that have an ETA in next 15 days
print db(((db.issues.eta_date > today) & (db.issues.eta_date <=
fifteen_days_ahead)) & (db.issues.workspace == user_workspace) &
(db.issues.created_by
== logged_in_user)).
Can you print out the raw SQL via ._select() so we can see exactly what is
being sent to the database when the error occurs?
On Monday, July 30, 2018 at 5:39:35 AM UTC-4, Rahul wrote:
>
> Okay I followed everyones instructions
> I installed psycopg2 and the application is using this by default.
Okay I followed everyones instructions
I installed psycopg2 and the application is using this by default. However
it is giving me the same errors I got before. I did not earlier use "%s" %
but in the example I provided I just gave it a try as somewhere I think it
referred to a string issue.
1
pg8000 has many problems, my first approach would be to simply install
psycopg2
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message
13 matches
Mail list logo
