Update the PostgreSQL timeline

[bmomjian]

Have you considered updating the PostgreSQL timeline? I use it for one of my slide decks and would love an updated version. Thanks.

[daamien]

Hi @bmomjian !

Thanks for your interest in this diagram ! I'm happy to see this is useful ! We also use in the dalibo training courses....

I stopped updating it a few years ago, because as time goes by, it becomes a real challenge to display so much information horizontally. Basically this is just a 20-generations family tree (a mono-parent family...) and like most family tree it's probably a better idea to use top-down design, but then that would be useless for a slide deck....

There may be a smarter way to this. Maybe a "Metro-Line map" type of design:

https://media.springernature.com/lw685/springer-static/image/art%3A10.1007%2Fs12650-021-00796-6/MediaObjects/12650_2021_796_Fig13_HTML.png

But that's beyond my modest grapĥic skills :-) Maybe someone in community could help with this ? or a paid freelance designer ? I guess it would not be that costly to get a data visualization professional to produce an updated map every year. Could this be a funded effort by a non-profit organization of the community (PGUS, PGEU, etc. ) ?

Another idea I had would be to develop an automated map in javascript. That map would be based on a JSON metadata file containing all forks. The result would be less pretty but we could easily maintain that metadata file with git commits (or even a SQL table exported in JSON 😏 ) and the map would be updated in real time:

Here's a quick example:

https://codepen.io/daamien/pen/BaYPGgO

Maybe both approaches are valid and could done in parallel : an automated javascript map based on a JSON metadata file and once a year a graphic designer would update a nice-and-shiny revamped version of the automated map ?

Anyway I'm open to ideas and suggestions about this.... Let me know what would be best for you !

``

[bmomjian]

Sorry for the late reply. No one has complained that it isn't current, so I guess I am okay for now. I just wanted to ask in case there was an easy solution, but it seems there is not. Thanks.

---

On Mon, Jun 6, 2022 at 04:23:19AM -0700, damien clochard wrote:

Hi @bmomjian !

Thanks for your interest in this diagram ! I'm happy to see this is useful ! We also use in the dalibo training courses....

I stopped updating it a few years ago, because as time goes by, it becomes a real challenge to display so much information horizontally. Basically this is just a 20-generations family tree (a mono-parent family...) and like most family it's probably a better idea to use top-down design, but then that would be useless for a slide deck....

There may be a smarter way to this. Maybe a "Metro-Line map" type of design:

https://media.springernature.com/lw685/springer-static/image/ art%3A10.1007%2Fs12650-021-00796-6/MediaObjects/12650_2021_796_Fig13_HTML.png

But that's beyond my modest grapĥic skills :-) Maybe someone in community could help with this ? or a paid freelance designer ? I guess it would be costly to get an updated map every year. could this be a funded effort by a non-profit organization of the community (PGUS, PGEU, etc. ) ?

Another idea I had would be to develop an automated map in javascript. That map would be based on a JSON metadata file containing all forks. The result would be less pretty but we could easily maintain that metadata file with git commits (or even a SQL table exported in JSON 😏 ) and the map would be updated in real time:

Here's a quick example:

https://codepen.io/daamien/pen/BaYPGgO

Anyway I'm open to ideas and suggestions about this.... Let me know what would be best for you !

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.*Message ID: <daamien/artwork @.***>

-- Bruce Momjian @.***> https://momjian.us EDB https://enterprisedb.com

Indecision is a decision. Inaction is an action. Mark Batterson