Open mkezfarias opened 4 years ago
property type would be normal / premium WATER BOILER, AIR CONDITIONING, STOVE, HEATER, OVEN could be all in a string or array.
WATER BOILER, AIR CONDITIONING, STOVE, HEATER, OVEN, The above should be included in perks or services
FURNISHED-DESCRIPTION TEXT
The above can be in the normal description
These three can all be the same right? Close amenities or something:
CLOSETO TRANSPORTATION BIG AVENUES AROUND
ABOUT CITY AREA
We can just pull this from google or wikipedia, not a unique information
I'm worried this table is getting too inflated, maybe we could create a propertyDetails table?
I agree greatly, let's do it that way, this approach would be cheaper in terms of memory when doing queries. We only need to get those details when viewing the property and not when indexing.
I put all of those fields separately to encourage landlords to fill out more information than other sites do. Those would be specific questions for them to fill out and display as such on the show page.
WATER BOILER, AIR CONDITIONING, STOVE, HEATER, OVEN, The above should be included in perks or services
I was thinking we could do something like this with those as hashes with booleans so we can add (didn't test, just writing pseudo pseudo code :)
That seems complex, are you thinking on storing that in the JSON format perhaps? Or just an array of objects?
I was thinking an array of objects, IDK what you think
for the properties model
we need TITLE STREET NAME HOUSE NUMBER NEIGHBORHOOD --- COLONIA CITY MUNICIPALITY ---DELEGACION LATITUDE / LONGITUDE FROM GOOGLE MAPS NUMBER OF BEDROOMS BATHROOMS AVAILABLE FROM DATE PRICE LEASE TYPE / regular or premium SECURITY DEPOSIT MINIMUN LEASE PROPERTY TYPE VERIFIED BOOLEAN MAIN DESCRIPTION GATED COMMUNITY / BUILDING PERKS PETS SPECIFIC RULES SERVICES INCLUDED FURNISHED BOOLEAN FURNISHED-DESCRIPTION TEXT WATER BOILER, AIR CONDITIONING, STOVE, HEATER, OVEN, PARKING INTEGER CLOSETO TRANSPORTATION BIG AVENUES AROUND ABOUT CITY AREA HASCONTRACT VISIT COUNT