On Tue, 2010-10-05 at 06:06 -0400, Luke wrote:
>
> That said, however, I have noticed a little apparent black-boxism in
> overall management. Discussions happen on subjects, then fall silent.
> Months later, a decision may be published. In the meantime, nobody
> outside has a clue what is go
On Tue, 2010-10-05 at 09:29 +0100, Stroller wrote:
> Stroller.
Thank you for you vent.
Sincerely,
Joshua D. Drake
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
h
On Mon, 2010-10-04 at 11:00 -0700, John Locke wrote:
> Hello,
> One other potential reason to move: the power tools for managing Drupal
> (drush being the main one) now depend on relatively recent versions of
> PHP -- at least PHP 5.2. Your server's reporting 5.1.6. That can mean
> the differen
ively easy and can be done by myself or one of my
staff.
3. A small www team to help manage content and keep the website up to
date.
This is the part that we need to community help on.
Sincerely,
Joshua D. Drake
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.com
can group billables into and
click "invoice"
Joshua D. Drake
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://iden
On Fri, 30 Jul 2010 07:21:34 -0400, "David F. Skoll"
wrote:
> If invoices are going to be non-editable, then I'd like to see
> a "Clone" button for posted invoices.
That's a pretty good idea.
JD
--
PostgreSQL - XMPP: jdrake(at)jabber(dot)postgresql(dot)org
Consulting, Development, Support, T
On Fri, 2010-07-30 at 00:13 -0400, Luke wrote:
> If there is a notes table:
>
> noteID (sequence)
> invoiceID
> type (enum: original, internal, additional)
> added (timestamp)
> note
>
> Originals can be created (unique per invoice) and viewed.
> Internals can be created and viewed.
> Additional
On Thu, 2010-07-29 at 21:53 -0500, John Hasler wrote:
> Joshua D. Drake writes:
> > I would go for permanent invoices AND non-editable invoices (notes not
> > included).
>
> Notes can be important and need to be preserved. How about permitting
> notes to be added bu
a mistake
and has been posted, you void it and create a new one.
Sincerely,
Joshua D. Drake
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, E
Hello,
What features would you like to see in 2.0?
The number one feature for me is:
# Updated and Modernized interface
Joshua D. Drake
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development
l CPA wants the job and charges less, then more
> power to him, but I doubt he will.
Exactly and that is what we do. CMD has a book keeper that works part
time, with our CPA to handle this stuff. Keeps it long out of the way,
out of my hair, and the cost to benefit analysis is much higher
On Wed, 28 Jul 2010 12:14:51 +0100 (BST), MJ Ray
wrote:
> Joshua D. Drake wrote:
>> FOSSExperts may be what you are looking for. Please feel free to bounce
>> over to : https://www.fossexperts.com/ and take a look.
>
> As a previous user of a similar site that has recentl
On Tue, 2010-07-27 at 15:49 -0700, Joshua D. Drake wrote:
> Hello,
> It is currently closed beta but I would open it up to specific well
> written proposals.
I just received a notice that there was an error in the registration
process. This is now fixed.
Sincerely,
Joshua
o
due to lack of funding?
FOSSExperts may be what you are looking for. Please feel free to bounce
over to : https://www.fossexperts.com/ and take a look.
It is currently closed beta but I would open it up to specific well
written proposals.
Sincerely,
Joshua D. Drake
--
PostgreSQL.org
On Tue, 2010-07-27 at 13:44 -0400, Armaghan Saqib wrote:
> On 07/27/2010 12:19 PM, Joshua D. Drake wrote:
> > On Tue, 2010-07-27 at 11:56 -0400, David F. Skoll wrote:
> >
> >> Joshua D. Drake wrote:
> >>
> >
> >> Or... figure out h
On Tue, 2010-07-27 at 11:56 -0400, David F. Skoll wrote:
> Joshua D. Drake wrote:
> Or... figure out how to get companies to pool resources... I don't
> need payroll support, but I'd be willing to contribute $100 for
> the feature. Find 200 people like me, and maybe you
us thread, we have
all these features were missing. I don't see a whole lot of people
stepping up to code or pay for them.
Sincerely,
Joshua D. Drake
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Cus
On Mon, 2010-07-26 at 20:31 -0500, John Hasler wrote:
> Joshua D. Drake writes:
> > I know many companies (mine included) that forgo the pain of payroll
> > and have a service do it.
>
> Sounds like much larger companies than I'm referring to.
Right and I think the larg
On Mon, 2010-07-26 at 17:18 -0500, John Hasler wrote:
> Joshua D. Drake writes:
> > There is a large swath of users that (millions) that if built properly
> > that we open up LedgerSMB to.
>
> Only when it handles payroll (in fact there's a large swath of users
>
On Mon, 2010-07-26 at 17:17 -0400, David F. Skoll wrote:
> Joshua D. Drake wrote:
>
> >> If you are dreaming of a situation in which LedgerSMB is used *and
> >> customized* by "average" office workers, I'd say LaTeX is the least of
> >> your wor
ging the CGI code to Catalyst Framework?
>
This is a possibility but honestly if I were to vote on moving to a
framework it would be with a move to Django or Pylons. Which wouldn't be
nearly as hard as it sounds as a large portion of our work is now *in*
DB
Sincerely,
Joshua D. Drake
--
On Sun, 2010-07-25 at 15:45 +, Jeff Kowalczyk wrote:
> Joshua D. Drake writes:
> > Lastly, for 2.0 we are moving to Git. We have already created the
> > repository and will slowly begin to populate over the coming months.
> >
> > http://github.com/commandprompt/L
On Sun, 2010-07-25 at 02:08 -0400, Luke wrote:
> On Sat, 24 Jul 2010, Joshua D. Drake wrote:
>
> > 2.0 of LedgerSMB is going to branch soon. The primary goal of 2.0 is to
>
> Is there any intent to do a final release of 1.3, or will it continue to
> be worked on concurren
aybe Joshua is on to something with XSLT. Maybe then the
> stuff could be sent to a good report generator or spreadsheet for
> formatting and printing. I bet Sue is expected to know how to use a
> spreadsheet. She does work in the accounting department, right?
Or is a book keeper for
On Sat, 2010-07-24 at 18:08 -0400, David F. Skoll wrote:
> Joshua D. Drake wrote:
>
> > Latex may be great for you but if I walk into an office and say, "Sue,
> > here is how you customize templates" and its tex? I might as well walk
> > back out, cause she wil
On Sat, 2010-07-24 at 16:24 -0400, David F. Skoll wrote:
> Joshua D. Drake wrote:
>
> > I firmly believe we need to eliminate Latex or at least not make it a
> > requirement and move to more modern technologies to generate invoices.
>
> What? Why? LaTeX produces beaut
/commandprompt/LedgerSMB
Sincerely,
Joshua D. Drake
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt
;mail($self->{from});
> $smtp->to($self->{to});
> $smtp->cc($self->{cc});
> $smtp->bcc($self->{bcc});
>
> $smtp->data();
> $smtp->datasend( $msg->as_string() );
> $smtp->dataend
h payroll.
It is really a matter of support from the community. Payroll is a huge
burden on a corporation. If there was enough financial support in the
community, it could definitely be built.
Joshua D. Drake
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.co
and reporting by a TAP harness, such as those
> used in Perl and PHP applications.
I know the author of this. It is a good project. I am not sure of the
applicability though I would have to look deeper.
Joshua D. Drake
-
John Hasler wrote:
> Joshua D. Drake writes:
>> Also, if you are going to join us on freenode at #ledgersmb we ask that
>> you continue to use the code of conduct and use paste sites. You may
>> find reference here:
>
> http://www.ledgersmb.org/conduct and http:/
going to join us on freenode at #ledgersmb we ask that
you continue to use the code of conduct and use paste sites. You may
find reference here:
http://www.ledgersmb.org/irc
Sincerely,
Joshua D. Drake
LedgerSMB Core
On Wed, 2008-06-04 at 21:40 +0100, Ed W wrote:
> Joshua D. Drake wrote:
> > Well one issue you are going to run into is cost. I don't know about
> > Chris but for us to do that you are going to have to come up with (even
> > with a discounted rate) 20k+. That is with
your priorities but we could easily handle the review portion
for a very reasonable fee and help make sure it gets committed.
And of course the other options is patience :). 1.3 is receiving a ton
of work right now and has been over the last several mont
loper, regardless of a committer
or not is welcome to submit a patch under the GPL and a committer (such
as myself, aurynn or chris) will review it for applicability.
Sincerely,
Joshua D. Drake
-
Check out the new SourceF
is a performance cost in large installations where these fields
> are used (AP/AP Reports, payment handling, etc). It should not
> affect most areas reports or data entry, however.
I would think the performance hit would be nominal except in the
largest of cases.
Joshua D. Drake
- --
The Post
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 13 Mar 2008 10:25:39 +
Ed Wildgoose <[EMAIL PROTECTED]> wrote:
> Joshua D. Drake wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On Tue, 11 Mar 2008 12:50:52 -0600
> > &quo
experience I can gain is invaluable.
So you modified our email sending routines to allow smtp-relay via
auth.. cool. How does it work? Does it support multiple users or is
there a "ledgersmb" user that sends etc...?
Can you send a patch for review?
Sincerely,
Joshua D. Drake
>
>
ake and test your changes to the local working copy.
>
> 3) svn diff and save the resulting unified diff as a patch file.
>
> 4) Submit via the project bug tracker, with notes on what the patch
> does, what branch to apply it to, how well it's been tested, etc.
>
> I thin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 22 Feb 2008 17:33:41 -0800
"Chris Travers" <[EMAIL PROTECTED]> wrote:
> Hi all;
>
> Any concerns about releasing 1.2.13 from the validation tarball.
>
> B est Wishes,
> Chris Travers
no
- --
The PostgreSQL Company since 1997: http://www.co
t will remain and continue to be present.
Nobody should be running LSMB on 8.3.0. Once 8.3.1 comes out, hopefully
LSMB wil have worked out its kinks enough as well to be supported fully.
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
Postgre
gt; http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=406935 (FWIW - we
> really could use help with this!)
Help with what exactly?
Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donat
Joshua D. Drake wrote:
> David A. Bandel wrote:
>> There is _nothing_ that suggests 8.3 isn't supported or won't work.
>> In fact, it looks like 8.1, not 8.2.6 is recommended.
>
> Looks like we need to update the website :).
Which is now done, in the FA
;
No. It is a fundamental change.
>> And if you want to try PostgreSQL 8.3 with LSMB experimentally (for the
>> purpose of providing bug reports, etc), you want to be running the
>> validation tarball of 1.2.13.
>
> I would be more than happy to do this if someone would tell
see it in other modules.
>
> Can provide the specific error, but anyone who's upgraded to 8.3
> should be seeing this. It's an integer = text (typecast) error.
With respect there is a reason that 8.3 isn't considered supported yet.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 16 Jan 2008 08:51:27 -0800
"Chris Travers" <[EMAIL PROTECTED]> wrote:
> On Jan 15, 2008 10:06 PM, Joshua D. Drake <[EMAIL PROTECTED]>
> wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
trunk (i.e. 1.3.x) please write back to the list which version
> you want to test with.
>
> At some point we should probably require 2.0.0 or higher so as to
> avoid too much duplicate code
We should not use any 2.0 specific features in 1.3.
Joshua D. Drake
>
> Best Wis
he server and the client.
Why not just have the stored procedures spit out an update as they are
working?
Processed 100 transactions
200 transactions
300 transactions
Until done. If you wanted to offset load, we can use plperl to implement
within the database with composite type, compound arrays.
Let's keep it standard relational please.
Sincerely,
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solut
Chris Travers wrote:
> On Nov 23, 2007 9:53 AM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
>>> 1: The database should be designed independently of the application
>>> at first. All fields in the database should be semantically atomic
>>> and shou
ssues pose substantial technical changes,
> and cannot happen anyway until we are ready to drop support for
> PostgreSQL 8.1. However, it is an area I would suggest we start
What is it about 8.1 that is limiting you here?
Sincerely,
Joshua D. Drake
- --
=== The PostgreSQL Comp
ve/kernel-resources.html
Once you are back up, run a VACUUM VERBOSE ANALYZE and report back the
last 5 lines again.
Sincerely,
Joshua D. Drake
> Charley
>
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Em
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 16 Nov 2007 18:49:59 -0600
Charley Tiggs <[EMAIL PROTECTED]> wrote:
> Joshua D. Drake wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On Fri, 16 Nov 2007 18:15:27 -0600
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 16 Nov 2007 18:15:27 -0600
Charley Tiggs <[EMAIL PROTECTED]> wrote:
> Joshua D. Drake wrote:
> >>> It sounds more like a machine level issue (bad configuration of
> >>> postgresql, not enough IO/RAM etc..)
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 16 Nov 2007 14:52:39 -0600
Charley Tiggs <[EMAIL PROTECTED]> wrote:
> Joshua D. Drake wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> > It sounds more like a machine level issue (bad configuration of
te that kind of situation.
To be frank that doesn't sound like a connection pool problem. I mean
how many connections is 30 orders creating?
It sounds more like a machine level issue (bad configuration of
postgresql, not enough IO/RAM etc..)
Sincerely,
Joshua D.
a previous post, we need to push
those into procs so we can just install the ones required based on the
version.
Joshua D. drake
signature.asc
Description: PGP signature
-
This SF.net email is sponsored by: Splunk Inc.
Still gre
e use something simpler, like BSD-style.
I think this license seems reasonable:
Attribution-Share Alike 3.0
http://creativecommons.org/licenses/by-sa/3.0/us/
http://creativecommons.org/licenses/by-sa/3.0/us/legalcode
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Comm
ly advocating one way or the other if you really want to
BSD it, go for it, you wrote most of it :)
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.comm
rward, then I will begin auditing
> contributions and contacting contributors to see if we can get the
> license terms for contributions relaxed.
I actually think I would prefer the Open Publication License:
http://www.opencontent.org/openpub/
Or perhaps the Creative Commons?
Joshua
re that any of the search stuff we
are doing is in procs, because our user space code won't change.
Joshua D. Drake
>
> Best Wishes,
> Chris Tavers
>
> -
> This SF.net email is sponsored by: Splunk Inc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Travers wrote:
> On 10/3/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> Apache/PostgreSQL authentication can still be done via any auth method. SSL
> would be nice for this leg but it is not where the issue is (which is
> b
.
We are making this far more complicated that it needs to be. Let's just
make it so ssl is part of the ledgersmb requirements and include the
docs to handle that. We can even include a simple wizard that will
create the postgresql ssl stuff.
Further, we should make it part o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Tangye wrote:
> On 10/3/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
>> Anyone who thinks a "user" should be able to install LSMB or PostgreSQL
>> is frankly, in a fantasy world.
>>
>
> OK I guess
ing http-auth would be a step backwards, given that
> some browsers are pretty unpredictable with the credentials (tell me a way to
> make a browser reliably "forget" credentials? afaik, there isn't one)
Yes there is. You close the browser. :)
Joshua D. Drake
- --
application that requires apache (unless we start shipping
an httpd server) is cause for removal from the "user" installing paradigm.
Sincerely,
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emerg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Nighswonger wrote:
> On 10/2/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Chris Nighswonger wrote:
>>> On 10/1/07, Chris Travers <[EMAIL PRO
he password to the DBI connect routine. Thus the only place
> the password is in plain text is in the connect routine. (One must
> wonder why the connect routine is not written to take hashed passwords
> to begin with.)
Or perhaps just require ssl connectivity to postgresql.
Joshua D. Dr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Travers wrote:
> On 10/1/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Chris Travers wrote:
>>> On 10/1/07, Joshua D. Drake <[EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Travers wrote:
> On 10/1/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
>> -
>>
>> passwords will not be stored as plain text... they will be an encrypted
>> hash. I am not understanding the problem.
>
&
red as plain text... they will be an encrypted
hash. I am not understanding the problem.
Joshua D. Drake
I don't think that this is acceptable as it both allows a set of
> trusted individuals to bypass security of the db and also undermines basic
> security mechanisms of PostgreSQL as a wh
are located in:
> Washington State, US,
> Oregon State, US,
I am in Washington now ;)...
Joshua D. Drake
> Alberta, Canada,
> Ontario, Canada,
> Rhode Island, US
> Quebec, Canada.
>
> We have other contribu
along again!
>
> There was a confusing reply to my post however...
>
> Joshua D. Drake wrote:
>>> As a matter of fact, I usually require the existence of an open Forum
>>> before seriously considering any software for use or recommendation.
>>> To
er
> relicense it.
Once dieters code is replaced, we can contact the handlful of authors
that are currently responsible for the code and change it should they
wish to.
There will be zero of dieter's code in this app by
the license as much as possible under the
> same spirit as possible under the GPL v2 or later circumstnaces that existed
> prior to the release of the GPL v3.
I am confused by this statement, GPL v2 is hardly the only major license
out there... Or maybe I am not understanding your point.
that work."
I think you are stretching here a bit. With Mono there is a distinct
difference in that you must "link" to mono (and
Source Software License" from the Open
Source Initiative?
Hmmm.. sounds like somebody has been sipping ;)
Sincerely,
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josh Berkus wrote:
> On Saturday 18 August 2007 10:47, Joshua D. Drake wrote:
>> As a core member, if it were up to me, we would ditch GPL all together.
>> I don't subscribe to the ideology present within it nor do I drink R
sn't with them, or the
> license... it's with your company.
Or its that the company that took the code has 22 million dollars in VC
that isn't their money in the first place and has a mar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christopher Murtagh wrote:
> On Saturday 18 August 2007 13:47:32 Joshua D. Drake wrote:
>> As a core member, if it were up to me, we would ditch GPL all together.
>
> Fortunately IMO, we're not able to do so without a t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Locke wrote:
> Hi,
>
> Joshua D. Drake wrote:
>> Hello,
> As a commercial company, I prefer releasing code under the GPL instead
> of the LGPL (or the Apache or the BSD licenses, etc), simply because it
> prevents co
f it were up to me and it isn't entirely. We would use either the LGPL
(version 2) or the OSL:
http://www.opensource.org/licenses/osl-3.0.php
Sincerely,
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800
he product and
not whether to upgrade to version 3 of a license. Not that the topic
isn't important, but that we have much bigger fish to fry right now.
Joshua D. Drake
>
> Can someone point me to a summary of what V3 actually says? V2 is
> poorly understood at the best of times,
eSQL does
it. With PostgreSQL a community member will start a project, and once
the project shows quality it gets inherited into the core project.
Examples of this include:
Planet PostgreSQL
Pg Buildfarm
Jabber
I would expect, should you want, the same thing would happen here.
Sincerely,
Josh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ed W wrote:
> Hi
ion is frequently better than it is on most
> mailing list archives). I guess it's just like the netnews guys who
> moan that it's a much better system than email, and yet how many
> projects reach for a newsgroup before they setup
t able to
help. Mailing list is where it is at, and proper disclosure of the
mailing list and insuring a friendly atmosphere will insure that.
Sincerely,
Joshua D. Drake
>
>
>
> -
> This SF.net ema
. and that itch to code started up. I've been
> working with Rails nearly exclusively for the past year, and I got used
> to its MVC framework.
>
> I know there are plans to use a TT as the templating engine. Are there
> plans to break out the code along MVC lines?
Yes but pr
py).
>
>
> Exactly.
Actually no. The taxman require that you be able to reproduce the
invoices not that they be paper (I know, I have been audited several
times, without any incident).
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
S
ry addresses)
Addresses (locations in the model) are completely separated from
everything already :)
Joshua D. Drake
>
> How does this sound? We probably don't want this to get
> overcomplicated, hence the suggestion just to duplicate records when
> they are changed and hide th
Chris Travers wrote:
> On 6/14/07, Josh Berkus <[EMAIL PROTECTED]> wrote:
>> All,
>>
>> The first text one reads on ledgersmb.org says:
>>
>> "LedgerSMB is a fork of a popular general ledger software package called
>> SQL-Ledger largely written and maintained by Dieter Simader.
>> SMB is an acronym
gt;
> Any other good hand-held web browsers that people might recommend?
Opera.
And which version of Pocket IE?
Joshua D. Drake
>
> Best Wishes,
> Chris Travers
>
> -
> This SF.net email is sponsor
Donna Robinson wrote:
> Hi,
>
> LedgerSMB version 1.2.5
Known problem. It is fixed in 1.2.6, ask Chris Travers for an updated file.
>
> Clicking on any of the foll (+) results in an error message:
>
> Purchases
> + Add Transaction
> + Creditor Invoice
> Reports
> + Transactions
>
Ed W wrote:
> Joshua D. Drake wrote:
>> Here is the current model:
>> http://ledger-smb.svn.sourceforge.net/viewvc/ledger-smb/trunk/sql/Pg-database.sql?view=markup&pathrev=1244
>>
>>
>
> Just shooting from the hip here:
>
> - Would be useful to be ab
. Sell is a task performed just as Buy is. A vendor
or customer is a class of entity.
> I do not think Class is a term that application end-users would so
> readily relate to. Then again, I am probably continuing to think of
> end-users as not being software-techoes, and this is
Here is the current model:
http://ledger-smb.svn.sourceforge.net/viewvc/ledger-smb/trunk/sql/Pg-database.sql?view=markup&pathrev=1244
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive
Hello,
I have just committed the first portions of the new entity/relationship
model. In turn, I have completely broke /trunk (which was expected).
However, if you want to see what is coming, the model does apply and you
can look at the relationships etc...
Joshua D. Drake
Hello,
I wanted to let all developers know that I will probably break trunk
over the next 10 days as I push out the crm database changes.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing
Chris Nighswonger wrote:
> Hi all,
> I'm beginning preliminary design work on a membership module for
> LedgerSMB. One of the basic features of this module will be attendance
> tracking. I would like to hear suggestions on how the relationship
> between members and events should be handled. Curre
right through team collaboration and positive
reinforcement (2x4, hose, or weed pulling with tweezers).
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive
ion or copying of this e-mail, including
attachments, is strictly prohibited.
--------
>>> "Joshua D. Drake" <[EMAIL PROTECTED]> 4/26/2007 4:06 PM >>>
Do you ha
1 - 100 of 162 matches
Mail list logo
