mastodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance, open to everyone, but mainly English and French speaking.

Administered by:

Server stats:

817
active users

#database

19 posts19 participants0 posts today

Check out Kothari Nishchay's session "PostgreSQL pgroll – Zero-Downtime, Reversible Schema Migrations" at #PostgreSQLDayBangkok to explore pgroll, a powerful tool for seamless database migrations.

🔗 Click here youtu.be/uB7egck68Js?si=WD2PXV to watch on the FOSSASIA YouTube channel

youtu.be- YouTubeEnjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

Watch Michael Paquier's session "AWS and the PostgreSQL Community" at #PostgreSQLDayBangkok to explore how AWS supports the PostgreSQL ecosystem, contributes to its development, and enhances database performance in the cloud.

🔗 Click here youtu.be/1-ds8RtLqt0?si=dTF_RO to watch on the FOSSASIA YouTube channel

youtu.be- YouTubeEnjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

Critical Minerals In Ores (CMiO) Database
--
lnkd.in/gynRjUfn <-- shared USGS publication
--
lnkd.in/gETca3DQ <-- shared link to open data database, web map services, etc
--
portal.ga.gov.au/persona/cmmi <-- shared web map
--
lnkd.in/gdmMp2zg <-- shared editorial piece on critical minerals and geopolitics
--
#geology #fedscience #opendata #CMMI #CMiO #criticalminerals #minerals #ores #database #opendata #GIS #spatial #mapping #spatialanalysis #commodities #technology #components #geochemistry #deposits #mining #extraction #classifaction #nomenclature #environments #structuralgeology #exploration
@USGS | @GeoscienceAustralia | @GeologicalSurveyOfCanada

Today I'm researching better workflows to backup databases, and create sanitised copies for local development.

I'm not able to find a great deal of informative discussion around best practice.

Is this stuff more obvious than I think - or is it so under-the-radar-unsexy that industry practice is just not very good?

🐘 Introducing: Prairie Postgres, a 501(c)(3) nonprofit organization chartered in Illinois, the Prairie State, serving the Midwestern United States!

We are devoted to training, professional development, and networking opportunities for technical practitioners and researchers.

For more information, check out our website: prairiepostgres.org

prairiepostgres.orgPrairie PostgresA 501(c)(3) nonprofit organization chartered in Illinois, the Prairie State, that serves the Midwestern United States. Focused on events, professional development, and networking opportunities for technical practitioners and researchers.

Is it a code smell for a table in Postgres to have mutually exclusive foreign keys?

For example, table A has foreign keys to table B and C, but there's a constraint in place where only one of those foreign keys can be populated.

My gut says I should be creating separate tables for these, as I'm effectively trying to tie a single table to multiple domain models (that happen to share the same fields).