On Thursday, June 15, 2017 at 10:32:22 AM UTC-7, icodk wrote:
>
> Sorry for the late response
> There is definitly a different if I use web2py shell source to send mail
> or web2py.exe
> It works fine with source and failes with web2py.exe
> My python installation is 2.7.13
>
As Massimo said
On Friday, June 16, 2017 at 4:23:15 PM UTC-4, jim kaubisch wrote:
>
> Hmmm,
>
> Chapter 7 of the book under "record versioning" says:
>
> Should you wish to access the archive table you should define it in a
> model:
>
> 1
> 2
> 3
>
> db.define_table('mytable_archive',
>Field('current_record'
Hmmm,
Chapter 7 of the book under "record versioning" says:
Should you wish to access the archive table you should define it in a model:
1
2
3
db.define_table('mytable_archive',
Field('current_record', 'reference mytable'),
db.mytable)
I want the option of looking into the Archive tabl
>
>Note: I'm unhappy about modifying the db.py file, but don't understand
> what happens if I allow the standard
>
> auth.define_tables(username=False, signature=False)
>
> in db.py, then later in my model file re-execute the
> auth.define_tables with signature=
Simple problem -- you are manually defining the archive tables, which you
are not supposed to do. When auth.enable_record_versioning() is called, it
notices the archive tables already exist, so it aborts and therefore never
adds the ._before_update callback that does the actual archiving. Just c
I have this in index.html before {{extend 'layout.html'}}
{{
response.title='My Site Name'
response.meta.keywords='web2py web development Denver'
response.meta.description='my description'
response.meta.author='my name'
}}
Most of the content of the page is in layout.html
#---
The auth.archive was an act of desperation - in case I had misinterpreted
something in the book. A last-minute addition. Lack of it off made no
difference to the outcome.
I'll try to generate a minimum app, but there are so many layers to the
original that it might be hard to reproduce more simp
Hello,
I uploaded a simple web2py app named 'mynotes', (based on markmin app
example) to gae under a project 'projectnotes' to keep my notes in. Very
simple model:
db.define_table('tblpage',
Field('page_title','string',label='Title'),
Field('page_text','text',label
I think that *flatpickr* should be the default datetime picker for the next
Web2py it looks awesome
On Monday, June 5, 2017 at 10:39:11 AM UTC+2, Karoly Kantor wrote:
>
> Dear Massimo,
>
> I saw your question in the developers group where I cannot post, therefore
> i do it here.
>
> I am current
Very impressive. Especially impressed by the 'Save for later' process,
which I bet I'll end up copying.
On Wednesday, 14 June 2017 14:36:18 UTC+1, Ian Ryder wrote:
>
> Hi all, not sure if it's OK to do this - slap me down if not!
>
> We're just about to launch a new tool / site based on web2py -
I think it depends on your database.
For postgres:
https://www.postgresql.org/docs/9.1/static/datatype-numeric.html
On Fri, Jun 16, 2017 at 3:16 PM, António Ramos wrote:
> Hello i´m using a table for a lot of similar stuff so it will grow very
> big.
> What is the limit for the id field? and w
Hello i´m using a table for a lot of similar stuff so it will grow very big.
What is the limit for the id field? and what happens when it reaches the
top?
Should i use an uuid ?
Regards
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py
Can you attach a minimal app (using SQLite) that reproduces the problem?
Also, do not use auth.archive in conjunction with
auth.enable_record_versioning (when working properly, that will cause
duplicates of archived records).
Anthony
On Friday, June 16, 2017 at 12:50:54 AM UTC-4, jim kaubisch
13 matches
Mail list logo
