On 23 March 2010 02:15, Craig White craigwh...@azapple.com wrote:
On Tue, 2010-03-23 at 03:02 +0100, Tony Tony wrote:
Craig White wrote:
I would have a table called pricing and have a column that had the
customer_id and thus you might have 2 (or more) prices for an item but
only one for a
On Tue, 2010-03-23 at 08:53 +, Colin Law wrote:
On 23 March 2010 02:15, Craig White craigwh...@azapple.com wrote:
On Tue, 2010-03-23 at 03:02 +0100, Tony Tony wrote:
Craig White wrote:
I would have a table called pricing and have a column that had the
customer_id and thus you
On 23 March 2010 15:08, Craig White craigwh...@azapple.com wrote:
On Tue, 2010-03-23 at 08:53 +, Colin Law wrote:
On 23 March 2010 02:15, Craig White craigwh...@azapple.com wrote:
On Tue, 2010-03-23 at 03:02 +0100, Tony Tony wrote:
Craig White wrote:
I would have a table called
Anybody have ideas, thoughts or suggestions?
-Tony
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Talk group.
To post to this group, send email to rubyonrails-t...@googlegroups.com.
To unsubscribe from
Craig White wrote:
I would have a table called pricing and have a column that had the
customer_id and thus you might have 2 (or more) prices for an item but
only one for a specific customer or default to the one that is not tied
to a specific customer.
Hi Craig!
I don't think this would
On Tue, 2010-03-23 at 03:02 +0100, Tony Tony wrote:
Craig White wrote:
I would have a table called pricing and have a column that had the
customer_id and thus you might have 2 (or more) prices for an item but
only one for a specific customer or default to the one that is not tied
to a
6 matches
Mail list logo
