Excellent. Exactly what I wanted.
Thanks a lot @cdbaron
On Saturday, July 17, 2021 at 6:22:36 PM UTC+5:30 cdbaron wrote:
> You should not use db.ftp_simplivity_log_db.log_path.readable = False
> You have to use db.ftp_simplivity_log_db.log_path.listable = False
>
> If you want to cancel the sear
You should not use db.ftp_simplivity_log_db.log_path.readable = False
You have to use db.ftp_simplivity_log_db.log_path.listable = False
If you want to cancel the search for any field in the table you can use
db.table.any_fielfd.searchable = Flase
El viernes, 16 de julio de 2021 a las 17:56:43
Can someone confirm my reasoning... or correct it if it's wrong?
Thanks,
Tom.
On Monday, May 10, 2021 at 3:22:24 PM UTC+2 Tom Clerckx wrote:
> I was running into some issue with SQLFORM.grid and after going through
> the code, I realized that the grid does not include request.vars when
> calcu
It works,
but the solution is db.table.field.listable = False to hide fields in the
gridand search, db.table.field.readable = False to hide fields and not
search and db.table.field.searchable = False to show Fields in grid and not
search.
El viernes, 1 de noviembre de 2019, 16:52:04 (UTC+1), P
If you want the fields to be searchable. Then instead of setting readable =
false.
Hide the fields with:
db.table.field.represent = lambda value, row: DIV(value, _class='hidden')
and the column heading with:
grid = SQLFORM.grid(
headers = {
'table.field' : DIV(_style = "display:N
>
> This is my code
>
def federados():
# Tablas de la BBDD
t_licencias = db.t_licencias
t_licencias_agrupaciones = db.t_licencias_agrupaciones
t_federados = db.t_federados
# Campos del grid
fields = [
t_federados.id,
t_federados.f_foto,
t_federado
On Saturday, August 17, 2019 at 9:22:15 AM UTC-7, Flavio Bovio wrote:
>
>
> *Add and edit button links are created incorrectly when the grid is inside
> another view. With the smartgrid works ok.*
>
> *Add button link*
> http://localhost:8000/erp_proto/tablas_grales/index/addt/forma_pago
Seems to me that it would as simple as using the buttonclass key as a name
or id in the gridbutton function. But I am not a professional so I don't
know if this is a good idea.
def gridbutton(buttonclass='buttonadd', buttontext=T('Add'),
buttonurl=url(args=[]), ca
Regardless - I think I found it:
Putting the following in the corresponding view does the trick:
jQuery(document).ready(function(){
jQuery('#w2p_keywords').css('width', '900px');
});
P.S. For anyone interested: In order to manipulate the object, you need to
know i
I'm on the latest master in Github (2018).
I am currently using the work-around below to fix the issue on all my
pages, simply by putting this line in my layout.html (which all my views
import):
path = window.location.pathname;
$(".web2py_console ").find('form').attr("action", path);
What web2py version are you using?
That was supposedly fixed here: https://github.com/web2py/web2py/pull/569
--
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)
Anthony, as always, thanks for correcting me
Jim
On Sat, Jun 16, 2018, 9:35 AM Anthony wrote:
> On Friday, June 15, 2018 at 12:57:54 PM UTC-4, watr wrote:
>>
>> Here is my links code:
>>
>> links = [
>> dict(header='Balance', body=lambda row: row.po.amount -
>> row.invoice_items.am
On Friday, June 15, 2018 at 12:57:54 PM UTC-4, watr wrote:
>
> Here is my links code:
>
> links = [
> dict(header='Balance', body=lambda row: row.po.amount -
> row.invoice_items.amount_pretax),
> dict(header='Controls', body=[
> lambda row: A('Invoices',_cla
On Saturday, June 16, 2018 at 10:03:37 AM UTC-4, Jim S wrote:
>
> Here is a sample we have where we add 'links'.
>
> links = [lambda row: A(XML(' Edit'),
>_href=URL('sample', 'sample', vars={'sample_id':
> row.sample.id}, user_signature=True),
>_clas
Here is a sample we have where we add 'links'.
links = [lambda row: A(XML(' Edit'),
_href=URL('sample', 'sample', vars={'sample_id':
row.sample.id}, user_signature=True),
_class='btn btn-default'),
lambda row: A(XML(' Reports'),
I've found a solution:
rows = db(db[table].id == id).select()
rendered_row = rows.render(0, fields=[db[table][column]])
value = rendered_row[column]
On Saturday, April 21, 2018 at 12:31:49 PM UTC+2, xelomac wrote:
>
> Thank you Anthony. Works perfectly in a SQLFORM.grid. The values get
> display
Thank you Anthony. Works perfectly in a SQLFORM.grid. The values get
displayed as expected.
But outside of the grid for something like this
persons = db(db[table].id == 1).select()
person=persons[0][column]
the stored values get displayed not its representation. How can I get the
representati
The validator controls the widget used in forms but no the format in the
grid -- for the latter, use the "represent" attribute:
represent=lambda v, r: GENDER[v]
Anthony
On Sunday, April 15, 2018 at 4:47:27 AM UTC-4, xelomac wrote:
>
> Consider the following example.
>
> Model:
>
> GENDER = {"ma
we should release a new version soon where font-awesome s the default.
On Wednesday, 7 March 2018 07:12:18 UTC-6, Esprit Garonne wrote:
>
> Many Thanks,
> Omg! I am really enjoying to test this framework.
>
> On Tuesday, March 6, 2018 at 8:33:26 PM UTC+1, Esprit Garonne wrote:
>>
>> Hello,
>>
Many Thanks,
Omg! I am really enjoying to test this framework.
On Tuesday, March 6, 2018 at 8:33:26 PM UTC+1, Esprit Garonne wrote:
>
> Hello,
> Does it a bug All buttons in SQLFORM have only text link. And I am working
> on school project for carpool, Could someone help me
> to build "etape
in latest version web2py use bootstrap 4 that is by default doesn't include
any icon for that, think you can try some of this option:
1. try trunk or github version, it included font awesome as an icon
2. put the icon by yourself in static/css side (font awesome or
glyphicons.css) and put it on v
The oncreate function is pointless because the only thing it does is
conditionally alter the form errors and vars, but then it redirects -- so
nothing happens with the altered form errors and vars (the redirect results
in a new request, so nothing from the current request is preserved).
You onv
I used the onvalidation() callback and it works like a charm.
And as a bonus I can invalidate the submit if my custom processing fails!
It's about a little more than a month i'm using Web2py and I still have to
get its "way of thinking" to implement some features.
Thanks Dave S!
Em terça-feira,
I'll take a look... I think it should work.
Thanks for the reply.
Em terça-feira, 26 de setembro de 2017 22:30:22 UTC-3, Dave S escreveu:
> Wouldn't you use the onvalidation() method? Look at
> http://web2py.com/books/default/chapter/29/07/forms-and-validators#SQLFORM-grid-signature
> >
> and
On Tuesday, September 26, 2017 at 6:00:27 PM UTC-7, Tiago Barrionuevo wrote:
>
> Hi!
> I'm trying to use custom forms for the actions used internally by the
> SQLFORM.grid and that are called by the grid links.
> I got all that working but now I need to do my own data manipulation after
> the
After researching the forum and other locations I found the following
"solution":
the raise HTTP(200) seems to break the running submit code. As suggested
elsewhere the download should be invoked on another page. So first redirect
and than start the download.
I replaced:
selectable = [('Dow
I will gladly test. But I can't do it until next week.
Sent from TypeApp
On 4 Aug. 2017, 17:58, at 17:58, Massimo Di Pierro
wrote:
>Just fixed in trunk. Can you please help test the fix?
>
>On Tuesday, 1 August 2017 03:46:13 UTC-5, Paul Ellis wrote:
>>
>> I am getting this error only when s
Just fixed in trunk. Can you please help test the fix?
On Tuesday, 1 August 2017 03:46:13 UTC-5, Paul Ellis wrote:
>
> I am getting this error only when searching the auth_membership table
>
> I have put in a basic 'appadmin' in my webapp. I call it 'tooladmin' to
> differentiate from the built i
Thanks for the suggestion! I added a header check for the
web2py-component-element header.
I had to manually add the value to response.headers (from request.cid)
because I'm using a call to web2py_component I guess. But it works
perfectly!!
On Thursday, August 3, 2017 at 6:28:07 PM UTC-7, Anth
Be careful that your page isn't making any other Ajax requests, as your code is
not limited to the component requests only.
Anthony
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issue
Thanks Anthony!! I resolved my problem with an ajaxSuccess event handler.
I am calling a web2py_component with the target div and using setTimeout to
achieve what I want. The code snippet in demo/f1.html is below for anyone
who may be interested:
my_url = "{{=URL('demo', 'f1.load')}}";
update_i
>
> I have an alert to verify that the data-w2p_remote is set correctly but
> the XHR is still made to the default page.
> Is there some sort of a trigger or a function that I can call that lets
> the code in web2py.js know that the URL in the data-w2p_remote attribute
> was changed?
> That wou
Thank you for your response.
As you suggested, I am currently trying to get around this by manually
adding the div layer (instead of LOAD helper) and setting the generated
link from the controller using response.js. Snippet below:
In demo/f1.html:
loading...
In controller f1:
url =
>
>
>1. My actual goal is to load this grid and keep refreshing it every 10
>seconds through XHR. For this, I created a simple view "demo/f1.load"
> which
>contains {{=grid}} and the "demo/f1.html" view has the following:
>{{=LOAD('demo', 'f1.load', ajax=True, content='Loading..
On Tuesday, July 25, 2017 at 8:32:55 PM UTC-4, Seth J wrote:
>
> I have a similar problem with maxtextlengths and I do have the "represent"
> attribute set like so:
> Field('f_last_change', type='text',
> label=T('Latest Changes'),
> defa
I have a similar problem with maxtextlengths and I do have the "represent"
attribute set like so:
Field('f_last_change', type='text',
label=T('Latest Changes'),
default = '',
represent=lambda text, row: HTML(XML('' i
thanks Peter, as for the grid i'm currently trying to work out how to
customize it, but yes i think the "buttons_placement = 'right' " puts the
buttons on the right
On Wednesday, July 5, 2017 at 4:39:17 AM UTC+2, Peter wrote:
>
>
> Glad you got something out of it Matt!
>
> I decided to try an
Glad you got something out of it Matt!
I decided to try and follow it through to the end but couldn't. (I did get
the grid check-boxes working but only if I selected just one report at a
time).
Your solution with the links is more user friendly (one click generates the
report) if you haven't
Thanks Peter - that was very helpful indeed. I didn't manage to get a
'download to CSV from checkboxes' function working, don't quite get why
as i managed to set up a 'download links from rows ' function in the
SQLFORM.grid.
Here is the code for you just in case it is any help for you in the fut
Based on previous code, the companies query/function would look something
like...
def csv_companies():
# assumes there is a table called 'company'with field 'name'
query = db.company.id > 0
companies = db(query).select(db.company.id,
thanks for your help Peter!
Actually, i've been playing around with it but need some into on
the functions/views too!
'The report_functions should point to valid report functions/views
that you have created (I can provide some info on this if needed)'
On Tue, Jul 4, 2017 at 4:37 AM, Peter
Hi Matt,
I'm no expert (only discovered the wonders of the grid in the last couple
of weeks) and maybe others
will have a better way but I have tested this and it might get you going...
(Also you might want to give a little more information on the
requirements...
Where have you got to?
Do t
Oh Yes !
Instead of an algorythm with variables and loops and
I saw this "belongs", but I hadn't imagined that it was the as the "IN" of
a select...
Thank you very much. I appologized, not to understand this myself :):):)
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentat
You probably want .belongs() with a nested ._select(), as shown here:
http://web2py.com/books/default/chapter/29/06/the-database-abstraction-layer#belongs
Anthony
On Monday, June 12, 2017 at 10:27:43 AM UTC-4, J-Michel Angers wrote:
>
> Hi,
> My app goes forward, I have plaisure to develop with
Thanks
I am a bit slow but I think I got it.
On Friday, June 2, 2017 at 4:41:39 AM UTC+2, Anthony wrote:
>
> On Thursday, June 1, 2017 at 5:52:08 PM UTC-4, icodk wrote:
>>
>> Thanks, That explain why it didn't work in smartgrid (because I haven't
>> specify the table name)
>> I still do not unde
Dave S.
I appreciate your responsiveness and alertness and the ever willingness to
help others.
Thanks
On Friday, June 2, 2017 at 6:37:03 AM UTC+2, Dave S wrote:
>
>
>
> On Thursday, June 1, 2017 at 6:19:02 PM UTC-7, Dave S wrote:
>>
>>
>>
>> On Thursday, June 1, 2017 at 2:52:08 PM UTC-7, icodk
On Thursday, June 1, 2017 at 6:19:02 PM UTC-7, Dave S wrote:
>
>
>
> On Thursday, June 1, 2017 at 2:52:08 PM UTC-7, icodk wrote:
>>
>> Thanks, That explain why it didn't work in smartgrid (because I haven't
>> specify the table name)
>> I still do not understand how my arguments will effect the
On Thursday, June 1, 2017 at 5:52:08 PM UTC-4, icodk wrote:
>
> Thanks, That explain why it didn't work in smartgrid (because I haven't
> specify the table name)
> I still do not understand how my arguments will effect the auto generated
> SQLFORM or what kind of argument will effect the form and
On Thursday, June 1, 2017 at 2:52:08 PM UTC-7, icodk wrote:
>
> Thanks, That explain why it didn't work in smartgrid (because I haven't
> specify the table name)
> I still do not understand how my arguments will effect the auto generated
> SQLFORM or what kind of argument will effect the form a
Thanks, That explain why it didn't work in smartgrid (because I haven't
specify the table name)
I still do not understand how my arguments will effect the auto generated
SQLFORM or what kind of argument will effect the form and in what way.
Is Niphlod's example is the only thing you can do with
On Wednesday, May 31, 2017 at 6:37:53 PM UTC-4, icodk wrote:
>
> Antony
> could you elaborate or give an example of how to use formargs,editargs
> etc. ?
>
When viewing/creating/updating individual records, the grid creates a
SQLFORM. You can use formargs, etc. to pass arguments directly to the
Thanks again Anthony,
To be honest that's a bit beyond my abilities at the moment though plenty
of food for thought!
I think I have a work around... essentially by doing the person search
before building the list for the grid.
i.e I can identify the person first and add person.id it to the qu
Antony
could you elaborate or give an example of how to use formargs,editargs etc.
?
You write that it can be used by passing it to SQLFORM but what could be
the actual use of it?
In another post
https://groups.google.com/forum/#!searchin/web2py/formargs$20field$20order%7Csort:relevance/web2py/c
>
> Is it possible to get the display_name (virtual field) to appear/behave as
> a 'normal' field in the grid?
>
No. Searching and sorting are handled via database queries, and the virtual
field values are not stored in the database but are calculated in Python
*after* records are fetched from
On Tuesday, April 25, 2017 at 9:19:59 AM UTC-5, Anthony wrote:
>
> On Tuesday, April 25, 2017 at 3:20:23 AM UTC-4, Jim Russell wrote:
>>
>> I worked around this by setting the wltype field to string and adding
>> a requires=IS_IN_SET. This makes the editing page have a dropdown with the
>> set
On Tuesday, April 25, 2017 at 3:20:23 AM UTC-4, Jim Russell wrote:
>
> I worked around this by setting the wltype field to string and adding
> a requires=IS_IN_SET. This makes the editing page have a dropdown with the
> set members instead of a free-form text field.
>
This is not a great idea if
On Tuesday, April 25, 2017 at 12:18:29 AM UTC-4, Jim Russell wrote:
>
> Hi all.
>
> I'm having an issue with an SQLFORM.gird query. I have a table where one
> of the columns references another table. Here are the table definitions:
>
> db.define_table('osrwhitelistpool',
> Field('id', type='id
On Tuesday, April 25, 2017 at 4:49:41 AM UTC-4, Gael Princivalle wrote:
>
> I can certainly do it finding the file that create this line.
> Someone knows which file is it?
>
> jQuery('#w2p_query_fields').change();jQuery('#w2p_query_panel').slideDown
> ();
>
If you want to take that approach, you c
SQLFORM.grid(..., advanced_search=False)
More generally, the "searchable" argument can be a callable that executes a
custom search, and the "search_widget" argument can be a callable that
generates a custom search widget for the UI. With the combination of those
two arguments, you can create wh
I can certainly do it finding the file that create this line.
Someone knows which file is it?
jQuery('#w2p_query_fields').change();jQuery('#w2p_query_panel').slideDown();
It doesn't matter if it'll delete this slidedown for all the application
grids.
Il giorno lunedì 24 aprile 2017 11:28:03 UT
I worked around this by setting the wltype field to string and adding
a requires=IS_IN_SET. This makes the editing page have a dropdown with the
set members instead of a free-form text field.
So it's working, but it's not the most elegant solution.
--
Resources:
- http://web2py.com
- http://we
I still don't know what caused this. There was obviously something missing
in the grid. I have come back to the problem after working around it with
js and can't replicate the issue. It is now working.
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.co
Here is the traceback:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
51.
52.
Traceback (most recent call last):
File "E:\web2py\gluon\restricted.py",
Oh I didn't know I could do that. That's perfect!
Thanks Edwin.
On Mon, Feb 13, 2017 at 8:59 PM, Edwin Haver wrote:
> Hi Paul,
>
> You can test if the grid has rows by doing the following
>
> {{if grid.rows:}}
> {{=grid.rows}}
> {{else:}}
> No records
> {{pass}}
>
>
> That should do it I th
Hi Paul,
You can test if the grid has rows by doing the following
{{if grid.rows:}}
{{=grid.rows}}
{{else:}}
No records
{{pass}}
That should do it I think.
Regards, Edwin
On Monday, February 13, 2017 at 7:12:53 PM UTC+4, Paul Ellis wrote:
>
> I want to display something else if the query
You could also do something like what is suggested here:
https://github.com/web2py/web2py/issues/1553#issuecomment-270406959. Though
as noted, the aggregate column will not be sortable, and you'd need to add
some code to remove the link in the UI that allows it to be selected for
sorting.
Anth
On Thursday, January 19, 2017 at 8:02:23 AM UTC-5, James Booth wrote:
>
> Hm, so there's no real way to do this at the minute?
>
> The problem is, if I do it via executesql or virtual fields, I can't
> export it as CSV which is my primary goal.
>
You could (a) create a view in the database to r
Hm, so there's no real way to do this at the minute?
The problem is, if I do it via executesql or virtual fields, I can't export
it as CSV which is my primary goal.
On Monday, January 16, 2017 at 1:01:01 PM UTC, Jurgis Pralgauskis wrote:
>
> Hi,
>
> I think it echoes my isssues
> https://github
Hi,
I think it echoes my isssues
https://github.com/web2py/web2py/issues/1559
https://github.com/web2py/web2py/issues/1553
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (
In my case, I have records with 2 fields, A & B; I want one record to be
displayed for each distinct value of A when B is either 1 or 2, but it is
possible that each will be present, so I use groupby A to avoid duplication.
I tried using a smartgrid, but it exhibited the same groupby/add behavio
This is tricky. Write operations (as well as the details view) are disabled
with groupby because the rows in the grid do not necessarily represent
individual records. Of course, that shouldn't necessarily preclude adding
new records, but from a user perspective, we have to think of what is meant
You can customize the search functionality by providing (a) a custom widget
via the "search_widget" argument (it takes a list of searchable fields and
a URL and should return a search form) and/or (b) a custom search query
builder via the "searchable" argument (it takes a list of searchable fiel
My bad; I was using concrete (the callback for AFTER a record has been
created) instead of onvalidation (the one for BEFORE that).
On Friday, December 2, 2016 at 11:17:57 PM UTC-5, Scott Hunter wrote:
>
> If the oncreate callback for a SQLFORM.grid sets form.errors to true, the
> record is not c
the body virtual field displays normally outside of a sqlform.grid.
--
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
On Thursday, September 22, 2016 at 2:14:41 PM UTC-4, Anthony wrote:
>
> On Thursday, September 22, 2016 at 6:45:55 AM UTC-4, Scott Hunter wrote:
>>
>> Because I don't need it. The original call tells me enough to make the
>> modifications I need to do, and then proceeds to build an up-to-date gri
On Thursday, September 22, 2016 at 6:45:55 AM UTC-4, Scott Hunter wrote:
>
> Because I don't need it. The original call tells me enough to make the
> modifications I need to do, and then proceeds to build an up-to-date grid,
> which becomes wasted effort because I'm getting a redirect re-build t
Because I don't need it. The original call tells me enough to make the
modifications I need to do, and then proceeds to build an up-to-date grid,
which becomes wasted effort because I'm getting a redirect re-build the
page I just built.
- Scott
On Wednesday, September 21, 2016 at 3:19:15 PM U
> The section of the online book about this says the lambda in the
>> selectable should be a redirect; when it was, I still got 2 requests, but
>> the second had an added var w/ the selected IDs.
>>
>
> The book doesn't say the callback should do a redirect -- that's just an
> example. In any
On Wednesday, September 21, 2016 at 1:16:29 PM UTC-4, Scott Hunter wrote:
>
> I think I understand; seems like something that should be documented, as
> well as able to be disabled.
>
Is it causing a problem for you? Why do you need to disable the redirect?
Anthony
--
Resources:
- http://web2p
I think I understand; seems like something that should be documented, as
well as able to be disabled.
On Wednesday, September 21, 2016 at 12:37:52 PM UTC-4, Anthony wrote:
>
> On Wednesday, September 21, 2016 at 9:36:14 AM UTC-4, Scott Hunter wrote:
>>
>> Here's a simple controller using an SQLF
On Wednesday, September 21, 2016 at 9:36:14 AM UTC-4, Scott Hunter wrote:
>
> Here's a simple controller using an SQLFORM.grid w/ selectable:
>
> def open_requests():
> print 'Req: %r' % request.vars
> query = ...
> form = SQLFORM.grid(query, csv=False, details=False, de
If I have the controller function return a string if there is a
'records' variable, the second request is not made; however, then it does
not redisplay the form.
On Wednesday, September 21, 2016 at 9:36:14 AM UTC-4, Scott Hunter wrote:
>
> Here's a simple controller using an SQLFORM.grid w/ sele
Although there is a "in", "contains" and "not in" now in the grid search
operator field, 'list:reference' - fields are not listed in the table
columns dropdown. Will it be possible to employ such operations with the
grid widget?
Am Dienstag, 5. April 2016 03:57:53 UTC+2 schrieb Massimo Di Pie
Ok, I missed that. As you describe it, it looks like a bug in the DAL Oracle
driver. Maybe you can document a simple example reproducing it and create an
issue, leaving out the grid references, it's just the query going wrong, right?
Issue tracker is located at
https://github.com/web2py/pydal
Nico,
Thanks for your response. The tables were already joined in the query
definition inside the controller.
query = ((db2.STATUSPOINT.POINTNUMBER < 100)&\
(db2.STATUSPOINT.POINTACCESSAREA == db2.AOR.AOR))
I feel quite certain that the problem is associated with the extra SQL
requ
Although it's been half a year; for the record, see this
post: https://groups.google.com/d/msg/web2py/6W-jf3EPb04/x3hSC5ySCgAJ
Op donderdag 28 juli 2016 10:17:50 UTC+2 schreef Ryan Hood:
>
> Hello,
>
>
>
> I'm pretty new to Web2py. I need some help with the SQLForm.grid export
> CSV function
Hello, has this already been updated. It seems that in the current version
it is still not possible. Is there a way to enable it by altering sqlhtml.py
for instance?
Would be very helpful to use this feature.
Thanks, Stephan
Am Dienstag, 5. April 2016 03:57:53 UTC+2 schrieb Massimo Di Pierro:
>
On Tuesday, July 26, 2016 at 10:29:26 AM UTC-7, icodk wrote:
>
> Dave S
> Thanks, you put me on the right track. What works for me is::
>
> db.tabl1.field1.widget= lambda f, v: SQLFORM.widgets.string.widget(f, v,
> _size=50)
>
> This is basically taken from Antony's post you pointed out.
> Your
Dave S
Thanks, you put me on the right track. What works for me is::
db.tabl1.field1.widget= lambda f, v: SQLFORM.widgets.string.widget(f, v,
_size=50)
This is basically taken from Antony's post you pointed out.
Your answer with form.custom does not apply because I have no form.custom.
The for
On Monday, July 25, 2016 at 2:25:32 PM UTC-7, rajjm...@gmail.com wrote:
>
> I have the same question. But for DAL in general. How to limit the string
> or text?
>
Field('myfield', 'string', length=32, ...)
This is described in the Field constructor documentation, but I'm not sure
there are a
I have the same question. But for DAL in general. How to limit the string
or text?
On Monday, July 25, 2016 at 5:00:49 PM UTC-4, icodk wrote:
>
> How can I change the input field size (what is visible to the user) of
> SQLFORM.grid auto generated Edit/New forms.
> Tried with length=50 but the fi
Thank you, Anthony!
I have found the same solution after reading the source code.
Maybe this tip is worth making mention of it in the book?
2016-05-24 17:16 GMT+02:00 Anthony :
> Rather than using the "fields" argument, to suppress a field in the grid,
> just set its "readable" attribute to Fals
Rather than using the "fields" argument, to suppress a field in the grid,
just set its "readable" attribute to False (before creating the grid):
db.t1.bb.readable = False
grid = SQLFORM.grid(db.t1)
Anthony
On Tuesday, May 24, 2016 at 8:44:53 AM UTC-4, mweissen wrote:
>
> Let's say I have table
Thanks Anthony,
I actually got it working using request.args(len(request.args)-1)
Your solution is far more elegant. I have not used python for a few years
and I forgot about slicing.
Thanks
Simon
On Monday, 9 May 2016 16:37:10 UTC+1, Anthony wrote:
>
> See my response here:
> https://groups.
See my response here:
https://groups.google.com/d/msg/web2py/covZOWYOQ1M/NyZkDW5IBAAJ
You need something like SQLFORM.grid(..., args=request.args[:1]).
Anthony
On Sunday, May 8, 2016 at 4:17:57 PM UTC-4, Simon Carr wrote:
>
> I think I now know why it's not working, but I don't know how to fix
I think I now know why it's not working, but I don't know how to fix it. I
think the issue is that I am filtering my supplier_contacts by getting the
supplier_id from request.args(0) however, the links on the SQLFORM.grid
look like this
http://127.0.0.1:8000/srm/supplier/view/view/supplier_cont
But the standard grid search widget never allowed for searching 'list:*'
fields (except for google:datastore).
Correct me if I'm wrong...
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2p
this should be fixed in trunk, we will release a new version.
On Sunday, 3 April 2016 02:21:38 UTC-5, Lionel Roubeyrie wrote:
>
> Hi all,
> I just start with this great framework and I have a similar issue. In a
> table there's two 'list:reference' Fields but none is searchable in the
> grid vie
Hi all,
I just start with this great framework and I have a similar issue. In a
table there's two 'list:reference' Fields but none is searchable in the
grid view.
Is there some special things to do before?
Le dimanche 8 novembre 2015 10:53:35 UTC+1, mweissen a écrit :
>
> I have a table like
>
On Tuesday, March 15, 2016 at 9:18:00 PM UTC-4, Vinyl Darkscratch-Kazotetsu
wrote:
>
> The *user_id* field is both non-readable and non-writable already, which
> is what's causing that error. It's not receiving any data for the field
> from anywhere. As for the various argument passing paramet
1 - 100 of 719 matches
Mail list logo
