On Tuesday, September 24, 2019 at 7:18:11 PM UTC-4, Ariel Juodziukynas wrote: > > Another option (if your database accepts it, like postgres or newer MySQL > versions) is to use a column with JSON or JSONB type. You could have a json > object with all property/value pairs. I'm not sure about performance, > indexing, etc on JSON columns though. > > I'm not sure what are the categories you are talking about now, you mean > the "auction type"? > > You'll have to have many many millions of auctions in order to make the > auction_properties tables too large (if your ID is an int, you have 2,000 > MILLION ids to use, if you use bigint I don't even know that number, you'll > need really good indexes though haha), and even if you ever get near some > critical situation you could split table by auction type or something like > that. I doubt it's something you have to worry about right now, you'll have > a lot of more important things to improve before reaching that. > > El mar., 24 sept. 2019 a las 19:19, fugee ohu (<[email protected] > <javascript:>>) escribió: > >> >> >> On Tuesday, September 24, 2019 at 12:37:37 AM UTC-4, [email protected] >> wrote: >>> >>> [response inline] >>> >>> On Mon, 23 Sep 2019 at 21:32, fugee ohu <[email protected]> wrote: >>> >>>> But then a single item will contain many records, one for each >>>> property, wouldn't that create too-large-tables? >>>> >>> >>> By the time that becomes a problem, you'll have bigger things to worry >>> about it, mate. -- H >>> >>> -- >>> OpenPGP: >>> https://sks-keyservers.net/pks/lookup?op=get&search=0xFEBAD7FFD041BBA1 >>> If you wish to request my time, please do so using >>> *bit.ly/hd1AppointmentRequest >>> <http://bit.ly/hd1AppointmentRequest>*. >>> Si vous voudrais faire connnaisance, allez a *bit.ly/hd1AppointmentRequest >>> <http://bit.ly/hd1AppointmentRequest>*. >>> >>> <https://sks-keyservers.net/pks/lookup?op=get&search=0xFEBAD7FFD041BBA1>Sent >>> >>> from my mobile devicet t >>> Envoye de mon portable >>> >> >> I can't make up my mind First, there's countless types of items Next >> they may use the category in deciding which form to load We haven't take >> categories into account yet in this discussion >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby on Rails: Talk" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/rubyonrails-talk/63f7e9f5-eb9a-4618-8ed9-d1f78f3a05b8%40googlegroups.com >> >> <https://groups.google.com/d/msgid/rubyonrails-talk/63f7e9f5-eb9a-4618-8ed9-d1f78f3a05b8%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > When you sell something on ebay there's no multiple choice of item type to sell, they figure out the type of item and the category from the title you provide but then ask you to confirm or change the category At this primitive stage I was thinking of adding an intermediate page to the new action to allow the user to select the type or category and then when they submit that page the relevant form will be on the next page There's such a thing as fallback also so I think I should build a rest framework first, I don't know
-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/38466182-5166-4205-9e65-22af3c4a3d6b%40googlegroups.com.
