« Return to Thread: autoincrementing invoices numbers
Re: autoincrementing invoices numbers
by cotanda
::
Rate this Message:
One simple question (and maybe a little naive: :$:$)
When you make an invoice, you don't call the post method on
class.ReceivableInvoice.inc.php ??
I am trying to do the next thing:
*When you add a new invoice you give it its invoice number, which won't
be necesarily definitive.
*When you post an invoice (you make it definitive) and you give as
invoice number the first "non posted" invoice number available. That way,
you swap both numbers.
*When you delete an invoice, you change its number with the last "non
posted" invoice number.
It's maybe a little weird, but this way you won't have to change posted
invoices (which is suposed to be imposible) when you delete an invoice, and
you won't get any jump in your posted (or not) invoices, even if the number
order will be the posting one and the invoice numbering could dance before
you post an invoice. It's posible to put messages informing the user when
adding a new invoice.
What do you thing... too weird???
Regards!
On Mon, 4 May 2009 09:13:57 -0600, Nathan Gray <nathan@...> wrote:
> On 4-May-09, at 3:15 AM, <cotanda@...> <cotanda@...>
> wrote:
>
>> Hi, sorry for being so late, I was on holidays xD
>>
>>> A global variable would not persist or be available for everyone.
>>> eGroupWare provides a table, egw_nextid, that lets you store the next
>>> number in a particular sequence.
>>
>> I have a concern about the egw_nextid table. You should start from 0
>> everytime you make a new installation or, if you want to have an
>> initial
>> number, you should add a field on the ar (and ap, etc) site
>> configuration
>> menu.
>
> Starting from 0 is easy, but it's easy enough to make that configurable.
>
>> Having a type field on the database would be not much space ...
>> The bad news on changing the database is that all the
>> insert queries should be changed to add the new field
>
> Not that hard, and a good idea.
> Done in SVN r3434, new column is named 'class'.
>
>> What do you think it would be more desirable? I would
>> try with the egw_nextid while I wait for answer ^^
>
> Adding the column was a good idea in general, so you have the option
> to do it whichever way works out best.
>
> Nathan Gray
> nathan at goarctic dot com
>
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Perp-developers mailing list
Perp-developers@...
https://lists.sourceforge.net/lists/listinfo/perp-developers
When you make an invoice, you don't call the post method on
class.ReceivableInvoice.inc.php ??
I am trying to do the next thing:
*When you add a new invoice you give it its invoice number, which won't
be necesarily definitive.
*When you post an invoice (you make it definitive) and you give as
invoice number the first "non posted" invoice number available. That way,
you swap both numbers.
*When you delete an invoice, you change its number with the last "non
posted" invoice number.
It's maybe a little weird, but this way you won't have to change posted
invoices (which is suposed to be imposible) when you delete an invoice, and
you won't get any jump in your posted (or not) invoices, even if the number
order will be the posting one and the invoice numbering could dance before
you post an invoice. It's posible to put messages informing the user when
adding a new invoice.
What do you thing... too weird???
Regards!
On Mon, 4 May 2009 09:13:57 -0600, Nathan Gray <nathan@...> wrote:
> On 4-May-09, at 3:15 AM, <cotanda@...> <cotanda@...>
> wrote:
>
>> Hi, sorry for being so late, I was on holidays xD
>>
>>> A global variable would not persist or be available for everyone.
>>> eGroupWare provides a table, egw_nextid, that lets you store the next
>>> number in a particular sequence.
>>
>> I have a concern about the egw_nextid table. You should start from 0
>> everytime you make a new installation or, if you want to have an
>> initial
>> number, you should add a field on the ar (and ap, etc) site
>> configuration
>> menu.
>
> Starting from 0 is easy, but it's easy enough to make that configurable.
>
>> Having a type field on the database would be not much space ...
>> The bad news on changing the database is that all the
>> insert queries should be changed to add the new field
>
> Not that hard, and a good idea.
> Done in SVN r3434, new column is named 'class'.
>
>> What do you think it would be more desirable? I would
>> try with the egw_nextid while I wait for answer ^^
>
> Adding the column was a good idea in general, so you have the option
> to do it whichever way works out best.
>
> Nathan Gray
> nathan at goarctic dot com
>
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Perp-developers mailing list
Perp-developers@...
https://lists.sourceforge.net/lists/listinfo/perp-developers
« Return to Thread: autoincrementing invoices numbers
| Free embeddable forum powered by Nabble | Forum Help |
