Since most orders contain line items, you might consider making an
order_header table that stores information about the order, then a
order_detail table that stores the information about each line item.
I don't do that. I would rather have orders than t_order how about
the_order :P
BR,
Jason
On Thu, Mar 10, 2011 at 6:13 PM, pbreit wrote:
> Yeah I saw that. What are people's thoughts on that? It seems like clutter
> to me but can definitely mak things easier in places.
Yeah I saw that. What are people's thoughts on that? It seems like clutter to
me but can definitely mak things easier in places.
I´m using f_ for fields and t_ for tables. The same way wizard creates
those.
Kenneth
I prefer to use singular names too, but I see it is clearly a good
idea to use plural ones as these seldom conflict.
How about 'request', 'requisition', 'purchase_order'. I sometimes make
up a word like 'p
I prefer to use singular names too, but I see it is clearly a good
idea to use plural ones as these seldom conflict.
How about 'request', 'requisition', 'purchase_order'. I sometimes make
up a word like 'porder'.
On Mar 10, 7:48 am, pbreit wrote:
> I'm so bummed I can't use the table name "orde
I'm so bummed I can't use the table name "order". So far I've considered
"orders" but that would be my only plural and "purchase". Are there any other
good names for orders. I know, this isn't world peace or anything.
order is a keyword in the database,
just change the table name to orders.
On Mar 9, 10:49 pm, Jamboo wrote:
> I tried making this simple database, and then tried the db admin panel
> and then a ticket gets generated. I tried copying the examples from
> Chapter 3 of the web2py book and I get the
7 matches
Mail list logo
