invoice number

[palanidharma]

hi all,

i am new to php.how to generate invoice number (EX:INV2008001) this format.

plz reply me the code....


thanks
palani

[MarkoKlacar]

Hi,

I can't spoonfeed you the code, but you'll want to have a look at rand as a start.

Should be pretty straight forward for you.

[Markus]

Hi,

I can't spoonfeed you the code, but you'll want to have a look at rand as a start.

Should be pretty straight forward for you.

That could produce a duplicate invoice number, though.

I think the best way would be to have an invoice number : INV20000001, and then increment that.

Save it in a db maybe.

[hsriat]

That could produce a duplicate invoice number, though.

I think the best way would be to have an invoice number : INV20000001, and then increment that.

Save it in a db maybe.

Or use this...
[php]
$new_invoice = gettimeofday();
$new_invoice = $new_invoice[sec];
[/php]

This will help if the invoice is generated not too fast. (Not more than once in a sceond)

[MarkoKlacar]

That's true, as you say you should have a combination.

My post was a bit clumsy, thanks for pointing it out.

[Markus]

Or use this...
[php]
$new_invoice = gettimeofday();
$new_invoice = $new_invoice[sec];
[/php]

This will help if the invoice is generated not too fast. (Not more than once in a sceond)

But still, it's not relevant to the invoices..

You'd typically (or is it just me) want to be able to keep track of the amount of invoices sent.. and don't invoice numbers generally go up as they are a way of tracking someone?

[hsriat]

But still, it's not relevant to the invoices..

You'd typically (or is it just me) want to be able to keep track of the amount of invoices sent.. and don't invoice numbers generally go up as they are a way of tracking someone?

Yeah, that will only help if you have to keep them unique. Not a counting of all.
But with this there is no db query required.

Or one other option can be...
- make a file with 0 written inside it.
- every time you create a new invoice, read that file and create the invoice like : [php]
//$file_content = content of the saved file
$invoice = "INV";
for ($i = 0; $i<10 - strlen($file_content); i++)
$invoice .= "0";
$invoice .= $file_content;

$file_content++;
//then save $file_content to the same file.
[/php]

[Markus]

I catch dig your jammin!

But, ultimately, it is better to use a database to keep track of records.

Look at us, i bet the OP has forgotten about this thread..

[hsriat]

I catch dig your jammin!

But, ultimately, it is better to use a database to keep track of records.

Look at us, i bet the OP has forgotten about this thread..

Yeh you are right in both the things...

1. Its better to use db, coz you might need to keep some other info about the invoice.. eg.. date, time, customer etc.

2. OP has forgotten about the thread.

[TheServant]

Good discussion though. How about using database table attributes:
INT(5) ZEROFILL AUTO_INCREMENT ? That way everytime a row is added it will increase by one but will appear as 00001 then 00002 etc...

Good idea/bad idea? I ask cos this is how I plan to set my system up.

[ronverdonk]

Good discussion though. How about using database table attributes:
INT(5) ZEROFILL AUTO_INCREMENT ? That way everytime a row is added it will increase by one but will appear as 00001 then 00002 etc...

Good idea/bad idea? I ask cos this is how I plan to set my system up.

Nothing wrong with the idea in itself, BUT ... never reorganize that table because your run the risk that it will be renumbered (assuming you sometimes delete rows from the table).

Ronald

[TheServant]

Nothing wrong with the idea in itself, BUT ... never reorganize that table because your run the risk that it will be renumbered (assuming you sometimes delete rows from the table).

Ronald

OK a little confused by what you mean. If i make a table:
00001 John
00002 Zed
00003 Adam

Then delete Row 2 (Zed). The next time I INSERT a row it will become:
00001 John
00003 Adam
00004 Tom

No repeat?

If I order by alphabetical order:
00003 Adam
00001 John
00004 Tom

Then INSERT a new row, I think it will be:
00003 Adam
00001 John
00004 Tom
00005 Wayne

Let me know if I am wrong, and also let me know if this is not what you meant. Thanks for your input!

[Markus]

Good discussion though. How about using database table attributes:
INT(5) ZEROFILL AUTO_INCREMENT ? That way everytime a row is added it will increase by one but will appear as 00001 then 00002 etc...

Good idea/bad idea? I ask cos this is how I plan to set my system up.

I like, and i didn't know about the ZEROFILL!
So it shall now be with me on my travels!

[TheServant]

I like, and i didn't know about the ZEROFILL!
So it shall now be with me on my travels!

w00t! I actually knew something someone didn't know! No offense markusn00b, u have already taught me so much, I'm glad to contribute something useful!

[Markus]

w00t! I actually knew something someone didn't know! No offense markusn00b, u have already taught me so much, I'm glad to contribute something useful!

Well, well!

Student has become the teacher!

[TheServant]

Anyway, Ronald, how about my question above?

[ronverdonk]

Anyway, Ronald, how about my question above?

Sorry, I have been away for a day.
What I meant is that when you REORGANIZE your table all the auto_increment values are also reorganized. So your table

00001 John
00003 Adam
00004 Tom
00005 Wayne

wll after the reorganize look:

00001 John
00002 Adam
00003 Tom
00004 Wayne

But of course, if you never reorganize, that's fine. And if your auto_increment numbers do not represent values like an invoice number, fine. My remark was just a liitle warning.

Ronald

[TheServant]

Sorry, I have been away for a day.
What I meant is that when you REORGANIZE your table all the auto_increment values are also reorganized. So your table

00001 John
00003 Adam
00004 Tom
00005 Wayne

wll after the reorganize look:

00001 John
00002 Adam
00003 Tom
00004 Wayne

But of course, if you never reorganize, that's fine. And if your auto_increment numbers do not represent values like an invoice number, fine. My remark was just a liitle warning.

Ronald

Fair enough. I think I am thinking of something different. When you say reorganise, do you mean ORDERBY or is there a REORGANISE function?

[ronverdonk]

Fair enough. I think I am thinking of something different. When you say reorganise, do you mean ORDERBY or is there a REORGANISE function?

The original question in this thread was about invoices.
By reorganize I mean just a SELECT INSERT sequence wehereby you get rid of the holes in your table sequences. MySQL does not have a REORGANIZE function (yet).

Ronald

[TheServant]

Sorry to go off topic a bit, but I think the OP has left:
If I have a hole and go INSERT, it shouldn't plug up the hole but continue the sequence. I have tried this before, so I guess I want to know how to plug that hole so I can avoid doing it!

[ronverdonk]

Sorry to go off topic a bit, but I think the OP has left:
If I have a hole and go INSERT, it shouldn't plug up the hole but continue the sequence. I have tried this before, so I guess I want to know how to plug that hole so I can avoid doing it!

This goes beyond the thread problem. I will ans wer this and then close this discussion. I was not talking about a simple INSERT, but re-arranging the auto_increment index into a new table using INSERT SELECT...

People do that because they have a very heavily changing table and are afraid that the auto_increment index is running out. (an INT as key and a million changes per day can get you into such a situation).


Ronald

[Markus]

Forgot to close it ;)