Here is a better example of what I mean.
in controller:
@auth.requires_login()
def foo():
row = db(db.mytable.id == auth.user_id).select().first()
return dict()
in scheduler.py
def sched_function():
row = db(db.mytable.id == auth.user_id).select().first()
return dict()
I am unable to fetch a row doing the same syntax in my scheduler function.
It returns an empty row. I also tried to include "@auth.requires_login" but
it doesn't seem to work.
sorry for the miscomunnication
On Jun 25, 2014, at 7:52 AM, Niphlod <niph...@gmail.com> wrote:
> there's no such thing (conceptually) as "tables that exists only if the user
> is logged in".
> the concept is "a user logged in can read/update/delete/etc some tables".
> That's what you do in "controllers".
> tables are "defined" (not accessed) instead in "models", so are available to
> everybody, scheduler included.
>
> On Wednesday, June 25, 2014 4:46:42 PM UTC+2, Cory wrote:
> I am trying to access tables that require the user to be logged in. Am I
> able to access these tables within my scheduler functions?
>
>
> On Wed, Jun 25, 2014 at 2:55 AM, Niphlod <nip...@gmail.com> wrote:
>
> why on hearth should you define tables based on the fact that a user is
> logged-in or not ?
> Scheduler functions are executed in a world that does not care for the usual
> request/response/session environment, and surely they do no count to be
> "logged in"...
>
> On Wednesday, June 25, 2014 12:53:57 AM UTC+2, Cory wrote:
> Hi,
> I am trying to access tables within my scheduler function. The tables I am
> trying to access require "@auth.requires_login()".
> Am I able to access these tables within my scheduler.py model file? right now
> I am passing table row fields as parameters
> to the scheduler function and it is very messy.
> In scheduler.py I have tried to include:
>
> db = DAL("postgres://postgres......blah)
> from gluon.tools import Auth
> auth = Auth(db)
>
> if auth.is_logged_in():
>
>
> thanks!
>
>
>
> --
> 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 a topic in the Google
> Groups "web2py-users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/web2py/_-MWC1WrOkY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> web2py+un...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 a topic in the Google
> Groups "web2py-users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/web2py/_-MWC1WrOkY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> web2py+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
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 the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
