Nice, I will check that out.
On Fri, Jun 28, 2013 at 1:37 PM, Anthony wrote:
> Yea thanks I tried that as well with no luck.
>
>
> Then you're doing something else wrong. It might help if you show all of
> the code. If you have a model file that does:
>
> db = DAL(...)
> ...
> auth = Auth(db)
>
Well whatever the case was it did give me some errors, cant remember which
now but I tried a few things to no avail.
I know its always this way starting out, been around the block a few times
already :)
On Fri, Jun 28, 2013 at 1:34 PM, LightDot wrote:
> On Friday, June 28, 2013 6:59:19 PM UTC+
>
> Yea thanks I tried that as well with no luck.
Then you're doing something else wrong. It might help if you show all of
the code. If you have a model file that does:
db = DAL(...)
...
auth = Auth(db)
auth.define_tables()
The db.auth_user will be available in any subsequent model as well as
On Friday, June 28, 2013 6:59:19 PM UTC+2, Tom Russell wrote:
>
> Yea thanks I tried that as well with no luck.
>
That's impossible. But never mind, hang in there, after you finish your
first project, you'll be remembering this beginnings with a smile.
> I ended up just creating a new db_wizar
Yea thanks I tried that as well with no luck. I ended up just creating a
new db_wizard.py in my model and this set up works great now. Its mentioned
in the book but thats it, just mentioned. For new users there should be a
guide to setting all of this up correctly. Maybe there is? I could write
som
Well, you have:
db = DAL('sqlite://storage.sqlite',pool_size=1,check_reserved=['all'])
defined, then you initiate auth with:
auth.define_tables(username=True, signature=True)
which sets up auth tables etc. in the above database. But then you override
the previously set db with:
db = DAL('sqli
6 matches
Mail list logo
