---------- Forwarded message --------- From: Howard Lowndes howard.lowndes@gmail.com Date: Wed, 29 Nov 2023 at 16:06 Subject: Dropping unwanted databases To: users@ledgersmb.org
In the process of setting up LedgerSMB and training users to the system I have created some, now, unwanted databases. Is there a way to drop these waifs with lamb_dbadmin or do I have to resort to postgres?
Howard,
As far as I know the only way to drop the database is using Postgres tools. That is how I do it anyway.
Neil
On Nov 29, 2023, at 6:06 PM, Howard Lowndes howard.lowndes@gmail.com wrote:
---------- Forwarded message --------- From: Howard Lowndes <howard.lowndes@gmail.com mailto:howard.lowndes@gmail.com> Date: Wed, 29 Nov 2023 at 16:06 Subject: Dropping unwanted databases To: <users@ledgersmb.org mailto:users@ledgersmb.org>
In the process of setting up LedgerSMB and training users to the system I have created some, now, unwanted databases. Is there a way to drop these waifs with lamb_dbadmin or do I have to resort to postgres?
-- Howard. -- When you want a computer system that works, just choose Linux; When you want a computer system that works, just, choose Microsoft.
-- Howard. -- When you want a computer system that works, just choose Linux; When you want a computer system that works, just, choose Microsoft. _______________________________________________ users mailing list -- users@lists.ledgersmb.org To unsubscribe send an email to users-leave@lists.ledgersmb.org
Hi Howard,
In the process of setting up LedgerSMB and training users to the system I
have created some, now, unwanted databases. Is there a way to drop these waifs with lamb_dbadmin or do I have to resort to postgres?
Personally I use the "dropdb" command with the postgres user, yes. From the web interface, there's no such functionality.
I know of phppgadmin that will provide a web based administration, and there may also be pgAdmin. What I would dearly like to do is use a "play" database to set up and refine the chart of accounts and then dump that CoA and import it into a live database as well as a training database.
I am also unable to use the bug-report.yml template despite being logged into Github. When I hover over the input fields I get a "No Entry" icon I've looked under the hood at the database structure and I am impressed and a little diffident about venturing too far though doing *select ** on the various *account* tables look to be the bulk of what I might need.
On Fri, 1 Dec 2023 at 08:20, Erik Huelsmann ehuels@gmail.com wrote:
Hi Howard,
In the process of setting up LedgerSMB and training users to the system I
have created some, now, unwanted databases. Is there a way to drop these waifs with lamb_dbadmin or do I have to resort to postgres?
Personally I use the "dropdb" command with the postgres user, yes. From the web interface, there's no such functionality.
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
Hi Howard,
On Fri, Dec 1, 2023 at 6:10 AM Howard Lowndes howard.lowndes@gmail.com wrote:
I know of phppgadmin that will provide a web based administration, and there may also be pgAdmin.
They will, indeed. The reason this functionality is currently missing isn't because we can't implement it. It's because we didn't want to expose an operation *this* destructive, potentially as exposed as over the web. Sure enough, when you know what you're doing, this isn't necessarily harmful. There are still people deploying LedgerSMB without https. In such situations it's good this functionality isn't in setup.pl.
What I would dearly like to do is use a "play" database to set up and refine the chart of accounts and then dump that CoA and import it into a live database as well as a training database.
So far, the import functionality has been much more important than the export functionality, but yes, I agree, this is now becoming a necessary feature. However, if you clean the following tables and copy their content to the other databases, you should be good:
* account * account_heading * account_translation * account_heading_translation * gifi * account_link * account_link_description (although this likely didn't change) * tax * cr_coa_to_account
There are many more tables linked to the "account" table, but on a database with only a CoA, those should be empty.
I am also unable to use the bug-report.yml template despite being logged into Github. When I hover over the input fields I get a "No Entry" icon I've looked under the hood at the database structure and I am impressed and a little diffident about venturing too far though doing *select ** on the various *account* tables look to be the bulk of what I might need.
I'm sorry you can't. I've reviewed all settings in the LedgerSMB "project" and the 'ledgersmb' "organization", but I can't find any settings that might prevent this access. I'll keep looking and discuss in the chat channel if others see why this might be the case.
Howard,
Did you try opening a blank issue. At the very bottom you should see “Open a blank issue” It would be interesting to know if this works?
Thanks,
Neil
On Nov 30, 2023, at 11:09 PM, Howard Lowndes howard.lowndes@gmail.com wrote:
I am also unable to use the bug-report.yml template despite being logged into Github. When I hover over the input fields I get a "No Entry" icon
participants (3)
-
Erik Huelsmann -
FWS Neil -
Howard Lowndes