let's start an argument about star trek. ready?
@Taweret no argument from me, because I'm one of those sickos that enjoys the animated series and personally considers it canon
On the other hand, I'm very much that kid who when asked, "would you like to teach the class?" has a history of saying yes and then knocking it out of the park. (I started in 4th grade)
I'm leaning toward either no or not yet, but I'm standing by for more information, clarifications, or a convincing argument for why this is a good idea. There are some things I could do better, but most of my reasons for leaving wouldn't be fixed just by my taking over because the problems originate external to that group.
@gnomon Octopus mugs. I'll post a picture if they come in. They're ordered but the company selling those doesn't believe in packaging materials for fragile products (but they're really good about issuing credits against the bill for stuff that arrives damaged).
@agudbrandson Got it. I'll take a look at that after the shop closes and see if I can figure anything out from that.
@agudbrandson Right, you shouldn't see anything until it finishes and the prompt returns (may take a while if the database is large). Once that's done, the file should exist in your home directory. You can ls to see it or see it in the Finder.
@agudbrandson You're missing some spaces there and need to do some more replacements with your own settings, but yeah, that's the general gist of things. What's the error it's throwing back?
@agudbrandson Replace x.y with the PostgreSQL version number, replace username with the database user Typica uses to connect to the database. Replace db_name with the name of the database that Typica connects to.
If you did that all right it'll ask for the password for that database user and then create a file called backup.db in your home directory.
@agudbrandson Okay, so on a Mac the installer usually doesn't put the pg* programs in $PATH, but under /Library/PostgreSQL/<version number>/bin where <version number> is replaced with the version of PostgreSQL you're using. If you open Terminal, you can:
cd /Library/PostgreSQL
ls
to see which version is there.
cd
to get back into your home directory and then /Library/PostgreSQL/x.y/bin/pg_dump -h localhost -U username -f backup.db db_name
Replacement instructions in the following reply.
@piggo Yes. I've written things basically architected like that. Sometimes it's kind of nasty because of bugs a compiler would have just failed on/worse debugger support, but if the native core is well thought out, feature development goes so much faster and you can often get customizations/fixes out to people without a need for changes in the core.
@cardassianvole Maybe they don't know. Male politicians in particular have repeatedly demonstrated a failure to grasp the basic biology involved.
@agudbrandson Sure. Let me know if you need help.
@agudbrandson Do you know how to use pg_dump? If so, and if you find that plan agreeable, you can upload the data at https://atelier.wilsonscoffee.com/s/e9fHwr99SDgcLrB
If not, let me know and I'll walk you through it.
@agudbrandson Not the database software, the data in the database. Something is going wrong there. I think what might be the fastest way to get this fixed would be if you could create a backup of your database with pg_dump and I'll be able to look at that and see if I can replicate the problem locally, figure out what's happening there, and see if it's repairable. If so, I'd fix the data, export it so you could reload that, and then delete my copy once you've succeeded.
Author of Typica software for coffee roasters.