I think I know what the problem is. I am defining tables in PHP my admin for mySQL. Is there a tool for web2py that will scan all the mysql tables in the database then update the db.py. Or is there a database GUI administration tool that I can use to create the tables within web2py.
On Feb 23, 10:18 am, stargate <kyoukh...@gmail.com> wrote: > I will send a screen shot when i get a chance. > > Thanks for all the help. > > On Feb 23, 9:16 am, Anthony <abasta...@gmail.com> wrote: > > > Can you send a screenshot of the page that is asking you for the user ID? > > Also, can you post the code from your model file where auth is defined? More > > details will help. > > > On Wednesday, February 23, 2011 9:08:32 AM UTC-5, stargate wrote: > > > It was asking me for the user generated ID > > > > On Feb 23, 8:21 am, Anthony <abas...@gmail.com> wrote: > > > > On Wednesday, February 23, 2011 7:11:08 AM UTC-5, stargate wrote: > > > > > > Yes but I click on the database administration within the new > > > > > application I have created. The database is connected to a mySQL > > > > > server. The issue is when i create a new table in the mySQL server it > > > > > doesn't show up under the Available databases and tables. So how do i > > > > > correct this. > > > > > Are you saying you have added a new table to the database outside of > > > web2py? > > > > If so, web2py won't know about it unless you create a model (i.e., using > > > > db.define_table) in your models file. Instead, you can create the web2py > > > > model first, and then web2py will create the table for you. > > > > > > Also when I add a new user > > > > > > here > > > > >http://127.0.0.1:8000/in2cu/appadmin/insert/db/auth_user > > > > > > I fill everything out but it asks me for a userID but this should be > > > > > generated automatically > > > > > Are you saying it's asking you for the auto generated record ID for the > > > new > > > > user -- that shouldn't be the case? Or is it asking you for a > > > > "username"? > > > By > > > > default, Auth uses the email address as the username for login. However, > > > if > > > > you use auth.define_tables(username=True), it will add a "username" > > > > field > > > to > > > > the user table -- perhaps that is what you are seeing (if there's an > > > actual > > > > "userID" field, perhaps that was added as a custom field). > > > > > Anthony > >