Search
List of Categories
Who has read this topic?
Add Reply
Printable version
Activate notificationNaming conventions » Mass change model info thread
Reminder of the previous message
For the record, the Big Dooley name was apparently used only by Chevrolet. GMC called these optional dual rear wheels... dual rear wheels. At least one reference to the Big Dooley option can be find in each 1973+ Chevrolet brochures, while none appears in the GMC ones as one can see in the following documents:
• 1973: GMC / Chevrolet;
• 1977: GMC / Chevrolet;
• 1985: GMC / Chevrolet;
• 1988: GMC / Chevrolet (note the use of the same picture in both brochures, with just a grille change
).
The other model years show the same difference...
Must an admin handle "manually" the deletion of this complement for the 24 concerned trucks (pure random choice: the one who ask for the renaming? ), or is this number "mass renaming" compliant?
• 1973: GMC / Chevrolet;
• 1977: GMC / Chevrolet;
• 1985: GMC / Chevrolet;
• 1988: GMC / Chevrolet (note the use of the same picture in both brochures, with just a grille change
).The other model years show the same difference...
Must an admin handle "manually" the deletion of this complement for the 24 concerned trucks (pure random choice: the one who ask for the renaming?
), or is this number "mass renaming" compliant?
For more than 10-15 it is ok for mass-change, but if you have time and want it quickly done (i.e. before this evening) it is up to you 
... though that when there are other info in the same field, it is not as easy
I know it can be done in SQL, but I'm always afraid of doing string handling in queries, since usually I don't achieve the right result the first time
So for these maybe better change them manually.
I know it can be done in SQL, but I'm always afraid of doing string handling in queries, since usually I don't achieve the right result the first time
So for these maybe better change them manually.
No problem to manage it manually. No hurry for it, so I'll make the changes little by little, together with the other things present on my to-do list 
Just for information:
I tested (and approved ) it several times, it just change the part you want to be changed.
(works of course also with where [FieldUsedAsKey] like '%[SearchedKey]%')
In the current case, the variables would be:
[FieldToBeModified] = Complement
[FieldUsedAsKey] = Make
[SearchedKey] = GMC
[StringToBeChanged] = Big Dooley
I think that the only trouble could be the blank spaces management, if [StringToBeChanged] is among other things, but it should be resolved by several passes:
• one with blank spaces before and after Big Dooley ([WantedString] being ' ' -just a blank space- then);
• one with a blank space just after, one with just before, and one without ([WS] = '' for these cases).
Just for information:
I tested (and approved
) it several times, it just change the part you want to be changed.- update [table] set [FieldToBeModified] = replace([FieldToBeModified], '[StringToBeChanged]', '[WantedString]') where [FieldUsedAsKey] = '[SearchedKey]'
(works of course also with where [FieldUsedAsKey] like '%[SearchedKey]%')
In the current case, the variables would be:
[FieldToBeModified] = Complement
[FieldUsedAsKey] = Make
[SearchedKey] = GMC
[StringToBeChanged] = Big Dooley
I think that the only trouble could be the blank spaces management, if [StringToBeChanged] is among other things, but it should be resolved by several passes:
• one with blank spaces before and after Big Dooley ([WantedString] being ' ' -just a blank space- then);
• one with a blank space just after, one with just before, and one without ([WS] = '' for these cases).
I think regexp can be used too, but then errors can occur even more easily
Though that for tests I can also limit the change to one particular vehicle_id and observe what happens...
Though that for tests I can also limit the change to one particular vehicle_id and observe what happens...
I think regexp can be used too [...]
Sometimes, I like to smash my fingers with a hammer too
[...] The bigger "mouth" - bumper grille - doesn't always have to indicate the 2003 facelift however. Some versions had this bumper already earlier...
What I understand as "bigger mouth / bumper grille" is the grille of the 2009+ 206+, i.e. more or less the one of a 207. I'm not sure we're talking about the same thing...
I meant the "high" spoiler containing the plate vs. the "small" one with a part of the plate on the grille.
It appears in fact that some cars with Phase 1 grille (horizontal bars) have the small spoiler that I only tied to the Phase 2 grille (egg crate one, from April 2003 onwards), and I also saw Phase 2 cars with the high spoiler. All vehicles that I have seen for now in the latter case are HDi, but I can't say if all 2003+ HDi are concerned.
In a nutshell, the front spoiler height can't be used as a clue to identify the registration year of a 206
Anyway, thanks for the MY changes.
Add Reply