christoph/fail
1
Fork 0
Code Actions Packages Releases Activity

dbcampaign: don't include fspmethod/variant ID in job msg

Browse Source 
These IDs don't make sense by themselves but only after a lookup in the
database, which clients usually don't have (and don't need) access to.

Conflicts:
	src/core/comm/DatabaseCampaignMessage.proto.in

Change-Id: Ice739463552039b7fb48581722ea2e05984cea47
This commit is contained in:
Horst Schirmeier
2014-07-04 16:27:31 +02:00
parent c422911741
commit d58694521c
2 changed files with 3 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
src/core/comm/DatabaseCampaignMessage.proto.in
View File

@ -8,8 +8,6 @@ import "@CONCRETE_INJECTION_POINT@";
message DatabaseCampaignMessage {
required uint32 pilot_id = 1 [(sql_primary_key) = true];
required uint32 variant_id = 2 [(sql_ignore) = true];
required uint32 fspmethod_id = 3 [(sql_ignore) = true];
// ToDo: injection_instr can be deleted if all experiments switched to
// using generic InjectionPointMessage
@ -27,4 +25,3 @@ message DatabaseExperimentMessage {
required uint32 bitoffset = 1 [(sql_primary_key) = true];
required uint32 original_value = 2;
}