[web2py] Add record button disappears when using groupby argument for SQLFORM.grid()

2016-12-21 Thread H. Das
Hello everyone, the add record button disappears when using groupby argument for SQLFORM.grid(). Is this normal behavior? How can I work around this without implementing my own add record feature? I'd really like to stay within vanilla grid as much as possible. Please advise. -- Resources: -

[web2py] Re: distinct keyword for SQLFORM.grid

2016-12-21 Thread H. Das
relevance/web2py/glEWmYRLSWQ/Y_bEVtZfPBoJ> However a distinct argument for grid would still be great. On Wednesday, December 21, 2016 at 3:56:13 AM UTC-5, H. Das wrote: > > Hi Massimo, I think this still hasn't been added yet. > > I too am doing several inner joins with grid a

[web2py] Re: distinct keyword for SQLFORM.grid

2016-12-21 Thread H. Das
Hi Massimo, I think this still hasn't been added yet. I too am doing several inner joins with grid and I'm getting some rows that I consider duplicates and would like to get rid of them. The most straightforward way to remove these duplicates is perhaps calling select() on the Set object with

[web2py] Re: Value error when forcing AM/PM time with time field

2016-08-30 Thread H. Das
Ok I found the problem. It turns out if I use IS_NOT_EMPTY(), the submitted time field values get treated like a string rather than a datetime.time object. Instead I changed requires to IS_TIME to get the intended result. On Monday, August 29, 2016 at 10:00:21 PM UTC-4, H. Das wrote

[web2py] Re: Value error when forcing AM/PM time with time field

2016-08-30 Thread H. Das
1:22:45 AM UTC-4, Dave S wrote: > > > > On Monday, August 29, 2016 at 7:00:21 PM UTC-7, H. Das wrote: >> >> Hello everyone, >> >> I defined a simple table with time fields like so: >> >> db.define_table("time_block", >> Field("st

[web2py] Value error when forcing AM/PM time with time field

2016-08-29 Thread H. Das
Hello everyone, I defined a simple table with time fields like so: db.define_table("time_block", Field("start_time", "time", requires=IS_NOT_EMPTY()), Field("end_time", "time", requires=IS_NOT_EMPTY()), ) In jQuery I forced the time widget to show AM/PM like so:

[web2py] Re: pyDAL support for crate.io ?

2016-08-17 Thread H. Das
at > feasibility. Do you think there is enough demand? Do you known if they (or > any other company) that may be interested in sponsoring this project? > > On Saturday, 6 August 2016 17:08:18 UTC-5, H. Das wrote: >> >> Are there any plans to support http://crate.io databa

[web2py] pyDAL support for crate.io ?

2016-08-06 Thread H. Das
Are there any plans to support http://crate.io database? I love crate.io's super simple scaling settings, and it would be amazing if pyDAL supported it. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) -

[web2py] generic.docx ?

2016-06-14 Thread H. Das
Would it be possible in web2py to create a generic.docx (word document, odf, or similar) template that can convert from HTML? Basically it should work just like generic.pdf. Thanks, love you guys. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) -

[web2py] Re: DAL not equal (!=) operator unexpectedly returning zero results

2016-04-23 Thread H. Das
Thanks! On Saturday, April 23, 2016 at 2:40:46 PM UTC-4, villas wrote: > > You can't compare NULL values using <>, you need this SQL: > > SELECT id, test_field FROM test_tableWHERE *(test_field <> "test_string")* OR > *(test_field is null)* > > Therefore use this query: >

[web2py] DAL not equal (!=) operator unexpectedly returning zero results

2016-04-23 Thread H. Das
I have a simple (SQLite) Table named *test_table*, and a simple Field called "test_field" like so: db.define_table('test_table', Field('test_field') ) Now when I populate this table in shell (or the app), and I try to do a query with (!=), something very weird and unexpected happens...

[web2py] How to make Autocomplete widget limit results based on previous fields?

2016-04-12 Thread H. Das
Hi, Currently I have a table defined like so: db.define_table("patient", Field('first_name'), Field('last_name'), Field('date_of_birth', 'date'), ) db.patient.first_name.widget=SQLFORM.widgets.autocomplete(request, db.patient.first_name, limitby=(0,10), min_length=1)

[web2py] Re: Sending email w/ text & html

2016-04-12 Thread H. Das
Hi can you try: mail.send(to='y...@example.com', subject=subject, message=msg, headers={'Content-Type' : 'text/html'}) On Tuesday, April 12, 2016 at 8:28:56 PM UTC-4, Scott Hunter wrote: > According to the current book, I should be able to do this: > > mail.send('y...@example.com ', >

[web2py] Re: How to add CSS classes to auth.login custom?

2014-04-18 Thread H. Das
Use jQuery: script $('form').attr({class:my-class}); /script On Wednesday, February 27, 2013 4:20:26 PM UTC-5, Chris wrote: Hello, I have a form that looks like this: {{top_login_form = auth.login(next = page_currentPath_get(request))}}

[web2py] Re: CAS Auth redirect loop

2012-08-13 Thread H. Das
I have the same problem too. I'm using custom auth_user table, as well as a custom decorator. After a new user registration, the browser returns a 310 error. I have to remove this custom decorator from *every *controller function for the problem to disappear during new registrations. This is

[web2py] possible bug with oauth20 facebook: auth.settings.login_next ignored in 1.84.4

2010-09-14 Thread H. Das
Hi, I think oauth20 ignores the url set for auth.settings.login_next (and maybe logout_next too?) in web2py 1.84.4; this wasn't the case in the previous version. Any ideas? Also, where can I find previous src's of web2py? Thanks :-)

[web2py] Re: possible bug with oauth20 facebook: auth.settings.login_next ignored in 1.84.4

2010-09-14 Thread H. Das
thank you both. On Sep 14, 4:34 pm, H. Das himel.p@gmail.com wrote: Hi, I think oauth20 ignores the url set for auth.settings.login_next (and maybe logout_next too?) in web2py 1.84.4; this wasn't the case in the previous version. Any ideas? Also, where can I find previous src's of web2py

[web2py] Re: possible error bug with oauth20 facebook documentation logout, respectively

2010-09-13 Thread H. Das
...@gmail.com wrote: Yes it is correct, in trunk you can find:    def logout_url(self, next=/):        del self.session.token        return next 2010/9/13 H. Das himel.p@gmail.com: Hi, in the documentation for oauth20 facebook section in chapter 8, the following correction

[web2py] possible error bug with oauth20 facebook documentation logout, respectively

2010-09-12 Thread H. Das
Hi, in the documentation for oauth20 facebook section in chapter 8, the following correction should be made: # import required modules from facebook import GraphAPI, GraphAPIError (the import of GraphAPIError is missing in the documentation) Also, i noticed that logging out when using this