Tag Info

New answers tagged

-1

You should go with mongoDB. My recommendation is to create a sharded environment using as shard key the restaurant identifier - i guess most of your queries will include that.


1

I sat down with management and said, "alright, what's the goal here?" Once we talked about it, they decided to let me write it in Python and use Postgres, since we use Postgres internally. I was able to convince them of that because of the dynamic libraries and the fact that I can tune the instance to cache everything and keep it in memory. So...a highly ...


1

I can only say that you have my deepest sympathies. Doesn't the person/company who/which is getting you to write a tool under this mind-boggling constraint realise that you'll have to do far more work for a far lesser return than if you used (as you say) "Python, Perl...". Anyway, what you wrote rang a very old bell in my memory cells - I remembered having ...


0

Use the official sample databases from MySQL: http://dev.mysql.com/doc/index-other.html.


0

MySQL can handle millions of records just fine and is one of the most prevalent databases available, so you will find plenty of support and tools on the web for it. There is little performance difference between MySQL and other databases like PostgreSQL (another fine Database). I regularly use http://excel2mysql.net to automate the import of 1 million+ ...


0

Here are some additional thoughts, from somebody who has designed an invoicing subsystem: What is apply_tax1 and apply_tax2? Why is late_fee a decimal? Why is it stored on the invoice? How will you keep track of updating the late_fee? Allowance and charge instructions, including late fees, typically belong to an Order. You do not have the concept of an ...


0

These are general recommendations, as you do not show the full extent of your queries to be performed (which kind of analytics you plan to do). Assuming you do not need real time results, you should just denormalize your data at the end of the period, precalculate once your aggregated results on all necessary timeframes -by day, by week, by month-, and work ...


0

I'd put person_id as second field of Report and get rid of notifier_type. Then create a relation persons (persona?) with id field, then make foreign key from Report.person_id to persons.id. This relation persons (persona?) would have all of fields from both your legal- and naturalPerson relations, plus one additional - person_type. You would have NULLs when ...



Top 50 recent answers are included