Thank you all for responding. With respect, I don't understand why COPY
gets related to ETL. All of the requirements I mentioned above have nothing
to do with ETL. We have a table of categories. A hierarchical table. This
is a multitenant app. Hundreds of thousands of records are in it. We want
to
Hello
Consider this scenario:
- 3 servers, 3 databases, each on a separate server:
- *Products database*: Contains the *Products* table (with over
100,000 records).
- *Taxonomy database*: Contains the *Categories* and *ItemCategories
(EAV)* tables.
- *Attributes d
in the ItemCategories table.
Thus, to show a list of 20 products on the website, this query first
fetches 100 thousand product_id values from the remote server.
That's not scalable. Is there a workaround for this?
Thank you
Saeed
On Wed, Mar 5, 2025 at 8:12 AM Adrian Klaver
wrote:
> On 3
I appreciate your time guys. Thank you very much.
> Having 1 table per database per server is too ugly.
Our databases are not one table per database. They are mapped to DDD's
bounded contexts and usually by one table per domain entity.
For example, we have these databases:
- Contacts
- Co
But then it seems to me that in this
case, Mongo would become a better choice because I lose the relational
nature and normalization somehow. What drawbacks have you experienced in
that sense?
Regards
Saeed
On Wed, Mar 5, 2025 at 7:38 PM Adrian Klaver
wrote:
> On 3/5/25 04:15, me nefcanto wrote:
we will migrate.
> Don't ever store arrays in the database. It will be a nightmare.
This is a very interesting claim. May I ask you to share its problems and
your experience?
On Thu, Mar 6, 2025 at 11:34 AM Laurenz Albe
wrote:
> On Thu, 2025-03-06 at 06:13 +0330, me nefcanto wrot
Hello
Please consider these scenarios:
- I want to create a million fake products, sometimes even 100 million
(we're on MariaDB now and we plan to migrate to Postgres). My team uses
fake data for performance tests and other use cases.
- Another scenario is translations. Even in production, we hav
Dear Laurenz,
That means a solid monolith database. We lose many goodies with that. As a
real-world example, right now we can import a single database from the
production to the development to test and troubleshoot data.
What if we host all databases on the same server and use FDW. What happens
i
:
> On Wed, 2025-03-05 at 10:12 +0330, me nefcanto wrote:
> > Adrian Klaver, thank you for the link. I asked the AI to create a query
> for me using FDW.
> >
> > The problem here is that it collects all of the product_id values from
> the ItemCategories table [...]
> &g
n I do for that?
Thank you for sharing your time. I really appreciate it.
Saeed
On Wed, Mar 5, 2025 at 3:18 PM Laurenz Albe
wrote:
> On Wed, 2025-03-05 at 14:18 +0330, me nefcanto wrote:
> > That means a solid monolith database. We lose many goodies with that.
> > As a real-w
10 matches
Mail list logo
