> Then why post?
>
> uff good thing i ran
--
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 this group, send email to
rubyonrails-talk+unsubscr...@
On 19 Sep 2010, at 21:03, Marnen Laibow-Koser wrote:
Although we could scope everything on the customer, but given the
total amount of data involved across all accounts, it would have a
dramatic impact on performance over time, even with proper indexes.
What makes you think so? A good DB sho
Peter De Berdt wrote:
[...]
> Since our main application is CRM and ERP, I'd like to chime in here.
>
[...]
>
> That said, we do have a separate database for every customer, for
> several reasons, I'll mention a few.
>
> Although we could scope everything on the customer, but given the
> total a
radhames brito wrote:
> For the developer is better to have one database but not for the
> clients,
> some may want their data exported in the future,
That's easy enough to do with one big database.
> or you may need to
> create
> extra id number in case some of then sequences for things like i
4 matches
Mail list logo
