fkey on data_source_id of sales_opportunity
Locked
fkey on data_source_id of sales_opportunity
 
|
Hi ,
Looks like the FKEY on data_source_id in relation sales_opportunity to data_source is missing. Am i missing something obvious ? regds mallah. Table "ofbiz.sales_opportunity" Column | Type | Modifiers -----------------------+--------------------------+----------- sales_opportunity_id | character varying(20) | not null opportunity_name | character varying(100) | description | text | next_step | text | next_step_date | timestamp with time zone | estimated_amount | numeric(18,2) | estimated_probability | numeric(18,6) | currency_uom_id | character varying(20) | marketing_campaign_id | character varying(20) | *data_source_id | character varying(20) | * estimated_close_date | timestamp with time zone | opportunity_stage_id | character varying(20) | type_enum_id | character varying(20) | created_by_user_login | character varying(255) | last_updated_stamp | timestamp with time zone | last_updated_tx_stamp | timestamp with time zone | created_stamp | timestamp with time zone | created_tx_stamp | timestamp with time zone | Indexes: "pk_sales_opportunity" PRIMARY KEY, btree (sales_opportunity_id) "sls_opprtnt_txcrts" btree (created_tx_stamp) "sls_opprtnt_txstmp" btree (last_updated_tx_stamp) "slsopp_crncy_uom" btree (currency_uom_id) "slsopp_mktgcmpg" btree (marketing_campaign_id) "slsopp_stage" btree (opportunity_stage_id) "slsopp_typ_enum" btree (type_enum_id) "slsopp_usrlgn" btree (created_by_user_login) Foreign-key constraints: "slsopp_crncy_uom" FOREIGN KEY (currency_uom_id) REFERENCES ofbiz.uom(uom_id) "slsopp_mktgcmpg" FOREIGN KEY (marketing_campaign_id) REFERENCES ofbiz.marketing_campaign(marketing_campaign_id) "slsopp_stage" FOREIGN KEY (opportunity_stage_id) REFERENCES ofbiz.sales_opportunity_stage(opportunity_stage_id) "slsopp_typ_enum" FOREIGN KEY (type_enum_id) REFERENCES ofbiz.enumeration(enum_id) "slsopp_usrlgn" FOREIGN KEY (created_by_user_login) REFERENCES ofbiz.user_login(user_login_id) |
Re: fkey on data_source_id of sales_opportunity
Administrator
|
Hi Rajesh,
Yes makes sense indeed, I see no reason to no have it as it's in all other cases. A Jira fits. Thanks Jacques Le 18/02/2019 à 20:00, Rajesh Mallah a écrit : > Hi , > > Looks like the FKEY on data_source_id in relation sales_opportunity > to data_source is missing. > > Am i missing something obvious ? > > regds > mallah. > > > > Table "ofbiz.sales_opportunity" > Column | Type | Modifiers > -----------------------+--------------------------+----------- > sales_opportunity_id | character varying(20) | not null > opportunity_name | character varying(100) | > description | text | > next_step | text | > next_step_date | timestamp with time zone | > estimated_amount | numeric(18,2) | > estimated_probability | numeric(18,6) | > currency_uom_id | character varying(20) | > marketing_campaign_id | character varying(20) | > *data_source_id | character varying(20) | * > estimated_close_date | timestamp with time zone | > opportunity_stage_id | character varying(20) | > type_enum_id | character varying(20) | > created_by_user_login | character varying(255) | > last_updated_stamp | timestamp with time zone | > last_updated_tx_stamp | timestamp with time zone | > created_stamp | timestamp with time zone | > created_tx_stamp | timestamp with time zone | > Indexes: > "pk_sales_opportunity" PRIMARY KEY, btree (sales_opportunity_id) > "sls_opprtnt_txcrts" btree (created_tx_stamp) > "sls_opprtnt_txstmp" btree (last_updated_tx_stamp) > "slsopp_crncy_uom" btree (currency_uom_id) > "slsopp_mktgcmpg" btree (marketing_campaign_id) > "slsopp_stage" btree (opportunity_stage_id) > "slsopp_typ_enum" btree (type_enum_id) > "slsopp_usrlgn" btree (created_by_user_login) > Foreign-key constraints: > "slsopp_crncy_uom" FOREIGN KEY (currency_uom_id) REFERENCES > ofbiz.uom(uom_id) > "slsopp_mktgcmpg" FOREIGN KEY (marketing_campaign_id) REFERENCES > ofbiz.marketing_campaign(marketing_campaign_id) > "slsopp_stage" FOREIGN KEY (opportunity_stage_id) REFERENCES > ofbiz.sales_opportunity_stage(opportunity_stage_id) > "slsopp_typ_enum" FOREIGN KEY (type_enum_id) REFERENCES > ofbiz.enumeration(enum_id) > "slsopp_usrlgn" FOREIGN KEY (created_by_user_login) REFERENCES > ofbiz.user_login(user_login_id) > |
Re: fkey on data_source_id of sales_opportunity
|
Administrator
|
Hi Rajesh,
If I dare ask: why did you not create a Jira? Thanks Jacques Le 19/02/2019 à 13:27, Jacques Le Roux a écrit : > Hi Rajesh, > > Yes makes sense indeed, I see no reason to no have it as it's in all other cases. A Jira fits. > > Thanks > > Jacques > > Le 18/02/2019 à 20:00, Rajesh Mallah a écrit : >> Hi , >> >> Looks like the FKEY on data_source_id in relation sales_opportunity >> to data_source is missing. >> >> Am i missing something obvious ? >> >> regds >> mallah. >> >> >> >> Table "ofbiz.sales_opportunity" >> Column | Type | Modifiers >> -----------------------+--------------------------+----------- >> sales_opportunity_id | character varying(20) | not null >> opportunity_name | character varying(100) | >> description | text | >> next_step | text | >> next_step_date | timestamp with time zone | >> estimated_amount | numeric(18,2) | >> estimated_probability | numeric(18,6) | >> currency_uom_id | character varying(20) | >> marketing_campaign_id | character varying(20) | >> *data_source_id | character varying(20) | * >> estimated_close_date | timestamp with time zone | >> opportunity_stage_id | character varying(20) | >> type_enum_id | character varying(20) | >> created_by_user_login | character varying(255) | >> last_updated_stamp | timestamp with time zone | >> last_updated_tx_stamp | timestamp with time zone | >> created_stamp | timestamp with time zone | >> created_tx_stamp | timestamp with time zone | >> Indexes: >> "pk_sales_opportunity" PRIMARY KEY, btree (sales_opportunity_id) >> "sls_opprtnt_txcrts" btree (created_tx_stamp) >> "sls_opprtnt_txstmp" btree (last_updated_tx_stamp) >> "slsopp_crncy_uom" btree (currency_uom_id) >> "slsopp_mktgcmpg" btree (marketing_campaign_id) >> "slsopp_stage" btree (opportunity_stage_id) >> "slsopp_typ_enum" btree (type_enum_id) >> "slsopp_usrlgn" btree (created_by_user_login) >> Foreign-key constraints: >> "slsopp_crncy_uom" FOREIGN KEY (currency_uom_id) REFERENCES >> ofbiz.uom(uom_id) >> "slsopp_mktgcmpg" FOREIGN KEY (marketing_campaign_id) REFERENCES >> ofbiz.marketing_campaign(marketing_campaign_id) >> "slsopp_stage" FOREIGN KEY (opportunity_stage_id) REFERENCES >> ofbiz.sales_opportunity_stage(opportunity_stage_id) >> "slsopp_typ_enum" FOREIGN KEY (type_enum_id) REFERENCES >> ofbiz.enumeration(enum_id) >> "slsopp_usrlgn" FOREIGN KEY (created_by_user_login) REFERENCES >> ofbiz.user_login(user_login_id) >> > |
Re: fkey on data_source_id of sales_opportunity
|
|
Hello,
I have created a JIRA ticket <https://issues.apache.org/jira/browse/OFBIZ-11218> for this. I will be uploading a patch soon. Thanks & Regards, Devanshu Vyas. On Fri, Sep 27, 2019 at 10:05 AM Jacques Le Roux < [hidden email]> wrote: > Hi Rajesh, > > If I dare ask: why did you not create a Jira? > > Thanks > > Jacques > > Le 19/02/2019 à 13:27, Jacques Le Roux a écrit : > > Hi Rajesh, > > > > Yes makes sense indeed, I see no reason to no have it as it's in all > other cases. A Jira fits. > > > > Thanks > > > > Jacques > > > > Le 18/02/2019 à 20:00, Rajesh Mallah a écrit : > >> Hi , > >> > >> Looks like the FKEY on data_source_id in relation sales_opportunity > >> to data_source is missing. > >> > >> Am i missing something obvious ? > >> > >> regds > >> mallah. > >> > >> > >> > >> Table "ofbiz.sales_opportunity" > >> Column | Type | Modifiers > >> -----------------------+--------------------------+----------- > >> sales_opportunity_id | character varying(20) | not null > >> opportunity_name | character varying(100) | > >> description | text | > >> next_step | text | > >> next_step_date | timestamp with time zone | > >> estimated_amount | numeric(18,2) | > >> estimated_probability | numeric(18,6) | > >> currency_uom_id | character varying(20) | > >> marketing_campaign_id | character varying(20) | > >> *data_source_id | character varying(20) | * > >> estimated_close_date | timestamp with time zone | > >> opportunity_stage_id | character varying(20) | > >> type_enum_id | character varying(20) | > >> created_by_user_login | character varying(255) | > >> last_updated_stamp | timestamp with time zone | > >> last_updated_tx_stamp | timestamp with time zone | > >> created_stamp | timestamp with time zone | > >> created_tx_stamp | timestamp with time zone | > >> Indexes: > >> "pk_sales_opportunity" PRIMARY KEY, btree (sales_opportunity_id) > >> "sls_opprtnt_txcrts" btree (created_tx_stamp) > >> "sls_opprtnt_txstmp" btree (last_updated_tx_stamp) > >> "slsopp_crncy_uom" btree (currency_uom_id) > >> "slsopp_mktgcmpg" btree (marketing_campaign_id) > >> "slsopp_stage" btree (opportunity_stage_id) > >> "slsopp_typ_enum" btree (type_enum_id) > >> "slsopp_usrlgn" btree (created_by_user_login) > >> Foreign-key constraints: > >> "slsopp_crncy_uom" FOREIGN KEY (currency_uom_id) REFERENCES > >> ofbiz.uom(uom_id) > >> "slsopp_mktgcmpg" FOREIGN KEY (marketing_campaign_id) REFERENCES > >> ofbiz.marketing_campaign(marketing_campaign_id) > >> "slsopp_stage" FOREIGN KEY (opportunity_stage_id) REFERENCES > >> ofbiz.sales_opportunity_stage(opportunity_stage_id) > >> "slsopp_typ_enum" FOREIGN KEY (type_enum_id) REFERENCES > >> ofbiz.enumeration(enum_id) > >> "slsopp_usrlgn" FOREIGN KEY (created_by_user_login) REFERENCES > >> ofbiz.user_login(user_login_id) > >> > > > |
Re: fkey on data_source_id of sales_opportunity
|
Administrator
|
Thanks Devanshu!
I'll have a look... Jacques Le 28/09/2019 à 09:35, Vyas a écrit : > Hello, > > I have created a JIRA ticket > <https://issues.apache.org/jira/browse/OFBIZ-11218> for this. I will be > uploading a patch soon. > > Thanks & Regards, > Devanshu Vyas. > > > On Fri, Sep 27, 2019 at 10:05 AM Jacques Le Roux < > [hidden email]> wrote: > >> Hi Rajesh, >> >> If I dare ask: why did you not create a Jira? >> >> Thanks >> >> Jacques >> >> Le 19/02/2019 à 13:27, Jacques Le Roux a écrit : >>> Hi Rajesh, >>> >>> Yes makes sense indeed, I see no reason to no have it as it's in all >> other cases. A Jira fits. >>> Thanks >>> >>> Jacques >>> >>> Le 18/02/2019 à 20:00, Rajesh Mallah a écrit : >>>> Hi , >>>> >>>> Looks like the FKEY on data_source_id in relation sales_opportunity >>>> to data_source is missing. >>>> >>>> Am i missing something obvious ? >>>> >>>> regds >>>> mallah. >>>> >>>> >>>> >>>> Table "ofbiz.sales_opportunity" >>>> Column | Type | Modifiers >>>> -----------------------+--------------------------+----------- >>>> sales_opportunity_id | character varying(20) | not null >>>> opportunity_name | character varying(100) | >>>> description | text | >>>> next_step | text | >>>> next_step_date | timestamp with time zone | >>>> estimated_amount | numeric(18,2) | >>>> estimated_probability | numeric(18,6) | >>>> currency_uom_id | character varying(20) | >>>> marketing_campaign_id | character varying(20) | >>>> *data_source_id | character varying(20) | * >>>> estimated_close_date | timestamp with time zone | >>>> opportunity_stage_id | character varying(20) | >>>> type_enum_id | character varying(20) | >>>> created_by_user_login | character varying(255) | >>>> last_updated_stamp | timestamp with time zone | >>>> last_updated_tx_stamp | timestamp with time zone | >>>> created_stamp | timestamp with time zone | >>>> created_tx_stamp | timestamp with time zone | >>>> Indexes: >>>> "pk_sales_opportunity" PRIMARY KEY, btree (sales_opportunity_id) >>>> "sls_opprtnt_txcrts" btree (created_tx_stamp) >>>> "sls_opprtnt_txstmp" btree (last_updated_tx_stamp) >>>> "slsopp_crncy_uom" btree (currency_uom_id) >>>> "slsopp_mktgcmpg" btree (marketing_campaign_id) >>>> "slsopp_stage" btree (opportunity_stage_id) >>>> "slsopp_typ_enum" btree (type_enum_id) >>>> "slsopp_usrlgn" btree (created_by_user_login) >>>> Foreign-key constraints: >>>> "slsopp_crncy_uom" FOREIGN KEY (currency_uom_id) REFERENCES >>>> ofbiz.uom(uom_id) >>>> "slsopp_mktgcmpg" FOREIGN KEY (marketing_campaign_id) REFERENCES >>>> ofbiz.marketing_campaign(marketing_campaign_id) >>>> "slsopp_stage" FOREIGN KEY (opportunity_stage_id) REFERENCES >>>> ofbiz.sales_opportunity_stage(opportunity_stage_id) >>>> "slsopp_typ_enum" FOREIGN KEY (type_enum_id) REFERENCES >>>> ofbiz.enumeration(enum_id) >>>> "slsopp_usrlgn" FOREIGN KEY (created_by_user_login) REFERENCES >>>> ofbiz.user_login(user_login_id) >>>> |
Re: fkey on data_source_id of sales_opportunity
|
Administrator
|
Done
Le 28/09/2019 à 10:08, Jacques Le Roux a écrit : > Thanks Devanshu! > > I'll have a look... > > Jacques > > Le 28/09/2019 à 09:35, Vyas a écrit : >> Hello, >> >> I have created a JIRA ticket >> <https://issues.apache.org/jira/browse/OFBIZ-11218> for this. I will be >> uploading a patch soon. >> >> Thanks & Regards, >> Devanshu Vyas. >> >> >> On Fri, Sep 27, 2019 at 10:05 AM Jacques Le Roux < >> [hidden email]> wrote: >> >>> Hi Rajesh, >>> >>> If I dare ask: why did you not create a Jira? >>> >>> Thanks >>> >>> Jacques >>> >>> Le 19/02/2019 à 13:27, Jacques Le Roux a écrit : >>>> Hi Rajesh, >>>> >>>> Yes makes sense indeed, I see no reason to no have it as it's in all >>> other cases. A Jira fits. >>>> Thanks >>>> >>>> Jacques >>>> >>>> Le 18/02/2019 à 20:00, Rajesh Mallah a écrit : >>>>> Hi , >>>>> >>>>> Looks like the FKEY on data_source_id in relation sales_opportunity >>>>> to data_source is missing. >>>>> >>>>> Am i missing something obvious ? >>>>> >>>>> regds >>>>> mallah. >>>>> >>>>> >>>>> >>>>> Table "ofbiz.sales_opportunity" >>>>> Column | Type | Modifiers >>>>> -----------------------+--------------------------+----------- >>>>> sales_opportunity_id | character varying(20) | not null >>>>> opportunity_name | character varying(100) | >>>>> description | text | >>>>> next_step | text | >>>>> next_step_date | timestamp with time zone | >>>>> estimated_amount | numeric(18,2) | >>>>> estimated_probability | numeric(18,6) | >>>>> currency_uom_id | character varying(20) | >>>>> marketing_campaign_id | character varying(20) | >>>>> *data_source_id | character varying(20) | * >>>>> estimated_close_date | timestamp with time zone | >>>>> opportunity_stage_id | character varying(20) | >>>>> type_enum_id | character varying(20) | >>>>> created_by_user_login | character varying(255) | >>>>> last_updated_stamp | timestamp with time zone | >>>>> last_updated_tx_stamp | timestamp with time zone | >>>>> created_stamp | timestamp with time zone | >>>>> created_tx_stamp | timestamp with time zone | >>>>> Indexes: >>>>> "pk_sales_opportunity" PRIMARY KEY, btree (sales_opportunity_id) >>>>> "sls_opprtnt_txcrts" btree (created_tx_stamp) >>>>> "sls_opprtnt_txstmp" btree (last_updated_tx_stamp) >>>>> "slsopp_crncy_uom" btree (currency_uom_id) >>>>> "slsopp_mktgcmpg" btree (marketing_campaign_id) >>>>> "slsopp_stage" btree (opportunity_stage_id) >>>>> "slsopp_typ_enum" btree (type_enum_id) >>>>> "slsopp_usrlgn" btree (created_by_user_login) >>>>> Foreign-key constraints: >>>>> "slsopp_crncy_uom" FOREIGN KEY (currency_uom_id) REFERENCES >>>>> ofbiz.uom(uom_id) >>>>> "slsopp_mktgcmpg" FOREIGN KEY (marketing_campaign_id) REFERENCES >>>>> ofbiz.marketing_campaign(marketing_campaign_id) >>>>> "slsopp_stage" FOREIGN KEY (opportunity_stage_id) REFERENCES >>>>> ofbiz.sales_opportunity_stage(opportunity_stage_id) >>>>> "slsopp_typ_enum" FOREIGN KEY (type_enum_id) REFERENCES >>>>> ofbiz.enumeration(enum_id) >>>>> "slsopp_usrlgn" FOREIGN KEY (created_by_user_login) REFERENCES >>>>> ofbiz.user_login(user_login_id) >>>>> > |
«
Return to OFBiz - User
|
1 view|%1 views
| Free forum by Nabble | Edit this page |