in table pp_notify - please define use of field "type"

[MediaHound]

In my database table pp_notify, there is a field entitled "type". Most users have type = 0 but there are a handful of type = 1.
Why are some set to 1 and most other notifications set to 0? What's the difference? When is type = 1 used?

The reason this is important to me is because I'm about to do a massive update to my database and change all the photos to "notify" instead of the default "don't notify", and I want to be clear what this field is for before I go and really make a mess.

Thanks in advance.

[Chuck S]

type 0 is for photo notifications and type 1 is category notifications

[MediaHound]

Thanks Chuck.

I have another related question.
What is the easiest way to make all my existing photos set to notify the member when he gets a comment posted to them?
I had a look at the database, and it involves some real fancy footwork to do it by hand in the db. That is, to add all the new ones, in addition to the existing ones, giving each a unique ID and appending the photo id with the owner id.
Do you have a simple solution for this?
I think such a tool do do this bulk change should be included in the default script, but that discussion is for a different topic all together, beyond the scope here...
Do you have some simple way for me to do this?
THANK YOU VERY MUCH, IN ADVANCE!!

[MediaHound]

As I await your kind reply , I'm still trying to whip up my SQL command to do this in one fell sweep. I pretty much have it ready..
Presuming you don't have an easy way to do this, could you just confirm with me that if I manufacture the proper sql code in the format:

Content visible to verified customers only.

where 242 = unique ID,
101 = user id,
2924 = photo id,
and 0 indicates this is an image, not a category,

If I get a nice text file / spreadsheet created with this format across every photo, and I insert it, would that be all I must do to solve my problem?
I did set new photos to default notify instead of default don't notify, so moving forward is no problem, but for these, if I do this, that's all that must be done?
To rephrase that , when a photo is set to notify the member of comments, is this the only table that is affected? If I insert my whipped up INSERT INTO commands, am I all set for what I want to accomplish?
I would of course make sure there are no duplicates...

PS, a bit off topic, but still on topic so to speak.. for all those people that want to do this themselves, to generate the unique ID's when I'm stuck in this situation, a quick visit to http://www.random.org/sequences (not my site) gets a lot of the dirty work done. You specify 1 then the highest number, submit, and there you have your numbers. You can then sort that ascending in excel.. sure beats typing out each number by hand or writing some script to do it.

[Chuck S]

You can not write a fancy sql statement

Each photo needs to have a query entered which means you need to write a script to do this

[MediaHound]

A sample few lines of what I manufactured:

Content visible to verified customers only.

I have it ready to insert, but before I do, I would just like to know if this is all that needs to be done, that there is not some other table that hooks into the process of notifications.
Thanks!

[Chuck S]

Notifications are all contained in the notify table

[MediaHound]

Thanks.
I will report back if there are any problems...

[MediaHound]

Ahh, one more thing. For the record, if anyone else were to do this, you should change the next auto-increment value.
Open phpMyAdmin, click your database, click the pp_notify table, then click "Operations" from the tabs on top. In there you will be able to change the auto_increment value. Make it something higher than where you are at now. The number you place there will be used for the next photo the scripts upload.