Re: problem Running with MS-SQL

2009-09-17 Thread Pankaj . Jain
Hi 

I also tried MSSQL by modifying unique="false" on some tables. It is 
building successfully. But without making any changes why it is running 
successfully in MySql ? If there is a problem in demo data or table 
structure it should give error on MySql also, but it is running fine 
there.

One more thing if we make these changes on MySql and other databases Will 
it affect their functionality ?

Thanks & Regards:

Pankaj Jain | L&T infotech |Navi Mumbai
Mobile: +91 9920218945
Email : pankaj.j...@lntinfotech.com
www.Lntinfotech.com

"Whatever the mind of man can conceive & believe, it can achieve."

Larsen & Toubro Infotech Ltd.
www.Lntinfotech.com

This Document is classified as: 

L&T Infotech Proprietary   L&T Infotech Confidential   L&T Infotech 
Internal Use Only   L&T Infotech General Business 

This Email may contain confidential or privileged information for the 
intended recipient (s) If you are not the intended recipient, please do 
not use or disseminate the information, notify the sender and delete it 
from your system. 

__

Re: Re: problem Running with MS-SQL

2009-09-04 Thread Mridul Pathak
t;, then started from creating a new database.
> >
> >  accounting\entitydef\entitymodel.xml
> > 1,931: 
> >
> >  marketing\entitydef\entitymodel.xml
> > 216: 
> >
> >  party\entitydef\entitymodel.xml (2 matches)
> > 714: 
> > 1,007: 
> >
> >  product\entitydef\entitymodel.xml (2 matches)
> > 1,839: 
> > 1,842: 
> >
> > I found demo data doesn't specify value for some of these fields, default
> > value of them is null. When inserting multiple records of data, demo data
> > seeding will get failure due to the unique index constrain.
> >
> > Thanks.
> > Weixue Zhang
> >
> > --
> > *发件人:* Abhijeet Pandey
> > *发送时间:* 2009-08-27  16:03:30
> > *收件人:* user
> > *抄送:* weixuezhang; Abhijeet Pandey
> > *主题:* Re: problem Running with MS-SQL
> >  *Hi Zhang,
> >
> > Thanks for this.
> >
> > Can you guide me that if i need to change all "unique=false" in all the
> > entitymodel.xml (there are about 26 of them)?
> >
> > Hi All,
> >
> >
> > Does anyone have an idea that why it happens with MSSQL ?
> >
> > Thanks ,
> >
> > Abhijeet Pandey
> > *
> >
> > On Sun, Aug 16, 2009 at 4:16 PM, Weixue Zhang  >wrote:
> >
> >>
> >> I am using ms sql server 2005 and this problem had bothered me for long
> >> time.
> >> At last I found it was caused by a few unique indices of some tables
> (You
> >> can find them by searching with "unique="true"" in files
> entitymodel.xml).
> >> After I changed them into "unique=false", demo data works fine. Can
> >> anybody
> >> explain why this problem doesn't exist with other database servers, and
> >> why
> >> we need to set unique=true at some indices while most others are
> >> unique=false?
> >>
> >> Weixue Zhang
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/problem-Running-with-MS-SQL-tp24895969p24992345.html
> >>  Sent from the OFBiz - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> > --
> > Abhijeet Pandey
> >
>
>
>
> --
> Abhijeet Pandey
>


Re: Re: problem Running with MS-SQL

2009-09-04 Thread Abhijeet Pandey
Hi,

i am able to connect to ofbiz with demo data after doing modification
suggested.

but i am not able to add product.

i am getting below error -->

 The Following Errors Occurred:

Error: Error trying to begin transaction, could not process method: The
current transaction is marked for rollback, not beginning a new transaction
and aborting current operation; the rollbackOnly was caused by: Failure in
create operation for entity [ProductDimension]:
org.ofbiz.entity.GenericEntityException: Error while inserting:
[GenericEntity:ProductDimension][brandName,null()][createdStamp,2009-09-04
19:05:12.577(java.sql.Timestamp)][createdTxStamp,2009-09-04
19:05:11.797(java.sql.Timestamp)][dimensionId,10003(java.lang.String)][internalName,A
Beautifull Mind(java.lang.String)][lastUpdatedStamp,2009-09-04
19:05:12.577(java.sql.Timestamp)][lastUpdatedTxStamp,2009-09-04
19:05:11.797(java.sql.Timestamp)][productId,BHV1(java.lang.String)][productType,Finished
Good(java.lang.String)] (SQL Exception while executing the following:INSERT
INTO OFBIZ.PRODUCT_DIMENSION (DIMENSION_ID, PRODUCT_ID, PRODUCT_TYPE,
BRAND_NAME, INTERNAL_NAME, LAST_UPDATED_STAMP, LAST_UPDATED_TX_STAMP,
CREATED_STAMP, CREATED_TX_STAMP) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) (The
statement was aborted because it would have caused a duplicate key value in
a unique or primary key constraint or unique index identified by
'SQL090811123924980' defined on 'PRODUCT_DIMENSION'.)). Rolling back
transaction.org.ofbiz.entity.GenericEntityException: Error while inserting:
[GenericEntity:ProductDimension][brandName,null()][createdStamp,2009-09-04
19:05:12.577(java.sql.Timestamp)][createdTxStamp,2009-09-04
19:05:11.797(java.sql.Timestamp)][dimensionId,10003(java.lang.String)][internalName,A
Beautifull Mind(java.lang.String)][lastUpdatedStamp,2009-09-04
19:05:12.577(java.sql.Timestamp)][lastUpdatedTxStamp,2009-09-04
19:05:11.797(java.sql.Timestamp)][productId,BHV1(java.lang.String)][productType,Finished
Good(java.lang.String)] (SQL Exception while executing the following:INSERT
INTO OFBIZ.PRODUCT_DIMENSION (DIMENSION_ID, PRODUCT_ID, PRODUCT_TYPE,
BRAND_NAME, INTERNAL_NAME, LAST_UPDATED_STAMP, LAST_UPDATED_TX_STAMP,
CREATED_STAMP, CREATED_TX_STAMP) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) (The
statement was aborted because it would have caused a duplicate key value in
a unique or primary key constraint or unique index identified by
'SQL090811123924980' defined on 'PRODUCT_DIMENSION'.)) (Error while
inserting:
[GenericEntity:ProductDimension][brandName,null()][createdStamp,2009-09-04
19:05:12.577(java.sql.Timestamp)][createdTxStamp,2009-09-04
19:05:11.797(java.sql.Timestamp)][dimensionId,10003(java.lang.String)][internalName,A
Beautifull Mind(java.lang.String)][lastUpdatedStamp,2009-09-04
19:05:12.577(java.sql.Timestamp)][lastUpdatedTxStamp,2009-09-04
19:05:11.797(java.sql.Timestamp)][productId,BHV1(java.lang.String)][productType,Finished
Good(java.lang.String)] (SQL Exception while executing the following:INSERT
INTO OFBIZ.PRODUCT_DIMENSION (DIMENSION_ID, PRODUCT_ID, PRODUCT_TYPE,
BRAND_NAME, INTERNAL_NAME, LAST_UPDATED_STAMP, LAST_UPDATED_TX_STAMP,
CREATED_STAMP, CREATED_TX_STAMP) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) (The
statement was aborted because it would have caused a duplicate key value in
a unique or primary key constraint or unique index identified by
'SQL090811123924980' defined on 'PRODUCT_DIMENSION'.)))   calling service
addProductToCategory in createProductInCategory



does the changes suggested below is the culprit ?


Plz guide.


Thanks,


Abhijeet Pandey


On Mon, Aug 31, 2009 at 5:42 AM, weixuezhang wrote:

>  Either demo data or entitymodel definition has problem. Can someone look
> into this problem?
>
> I found 6 places with unique="true" in trunk as below. I simply changed
> "true" into "false", then started from creating a new database.
>
>  accounting\entitydef\entitymodel.xml
> 1,931: 
>
>  marketing\entitydef\entitymodel.xml
> 216: 
>
>  party\entitydef\entitymodel.xml (2 matches)
> 714: 
> 1,007: 
>
>  product\entitydef\entitymodel.xml (2 matches)
> 1,839: 
> 1,842: 
>
> I found demo data doesn't specify value for some of these fields, default
> value of them is null. When inserting multiple records of data, demo data
> seeding will get failure due to the unique index constrain.
>
> Thanks.
> Weixue Zhang
>
> --
> *发件人:* Abhijeet Pandey
> *发送时间:* 2009-08-27  16:03:30
> *收件人:* user
> *抄送:* weixuezhang; Abhijeet Pandey
> *主题:* Re: problem Running with MS-SQL
>  *Hi Zhang,
>
> Thanks for this.
>
> Can you guide me that if i need to change all "unique=false" in all the
> entitymodel.xml (there are about 26 of them)?
>
> Hi All,
>
>
> Does anyone have an idea that why it happens with MSSQL ?
&g

Re: Re: problem Running with MS-SQL

2009-09-01 Thread Abhijeet Pandey
Hi Thanks,

it worked.

Thanks,

Abhijeet

On Mon, Aug 31, 2009 at 5:42 AM, weixuezhang wrote:

>  Either demo data or entitymodel definition has problem. Can someone look
> into this problem?
>
> I found 6 places with unique="true" in trunk as below. I simply changed
> "true" into "false", then started from creating a new database.
>
>  accounting\entitydef\entitymodel.xml
> 1,931: 
>
>  marketing\entitydef\entitymodel.xml
> 216: 
>
>  party\entitydef\entitymodel.xml (2 matches)
> 714: 
> 1,007: 
>
>  product\entitydef\entitymodel.xml (2 matches)
> 1,839: 
> 1,842: 
>
> I found demo data doesn't specify value for some of these fields, default
> value of them is null. When inserting multiple records of data, demo data
> seeding will get failure due to the unique index constrain.
>
> Thanks.
> Weixue Zhang
>
> ------
> *发件人:* Abhijeet Pandey
> *发送时间:* 2009-08-27  16:03:30
> *收件人:* user
> *抄送:* weixuezhang; Abhijeet Pandey
> *主题:* Re: problem Running with MS-SQL
>  *Hi Zhang,
>
> Thanks for this.
>
> Can you guide me that if i need to change all "unique=false" in all the
> entitymodel.xml (there are about 26 of them)?
>
> Hi All,
>
>
> Does anyone have an idea that why it happens with MSSQL ?
>
> Thanks ,
>
> Abhijeet Pandey
> *
>
> On Sun, Aug 16, 2009 at 4:16 PM, Weixue Zhang wrote:
>
>>
>> I am using ms sql server 2005 and this problem had bothered me for long
>> time.
>> At last I found it was caused by a few unique indices of some tables (You
>> can find them by searching with "unique="true"" in files entitymodel.xml).
>> After I changed them into "unique=false", demo data works fine. Can
>> anybody
>> explain why this problem doesn't exist with other database servers, and
>> why
>> we need to set unique=true at some indices while most others are
>> unique=false?
>>
>> Weixue Zhang
>> --
>> View this message in context:
>> http://www.nabble.com/problem-Running-with-MS-SQL-tp24895969p24992345.html
>>  Sent from the OFBiz - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Abhijeet Pandey
>



-- 
Abhijeet Pandey


Re: problem Running with MS-SQL

2009-08-30 Thread Vince Clark
I have run into this problem with SQL Server also. Dropping unique indexes 
takes care of it. However, I am also running into serious problems with 
deadlocks in SQL Server when loading large amounts of data programatically with 
simple methods. Everything I have read suggests indexes could be the culprit, 
but I haven't made the connection.

Vince Clark 
www.globalera.com 
vcl...@globalera.com 
(303) 493-6723 office
(303) 523-4843 cell 


- Original Message -
From: "David E Jones" 
To: user@ofbiz.apache.org
Sent: Sunday, August 30, 2009 8:59:21 PM GMT -07:00 US/Canada Mountain
Subject: Re: problem Running with MS-SQL


This sounds like one of those MS-SQL quirks with unique indexes where  
it only allows one row with each possible value, including null. In  
other words, there can only be one record with a null value in that  
column. If I remember right this has come up before too...

There may be a way to change the ALTER statement that adds the index  
to tell it to not include null. It would be nice if that was the  
default since the whole notion is silly, but that's just my subjective  
opinion and obviously theirs is different.

-David


On Aug 30, 2009, at 8:00 PM, Scott Gray wrote:

> Hi Weixue,
>
> Could you point me to an example of where the demo data violates a  
> unique constraint?
>
> Thanks
> Scott
>
> HotWax Media
> http://www.hotwaxmedia.com
>
> On 31/08/2009, at 12:12 PM, weixuezhang wrote:
>
>> Either demo data or entitymodel definition has problem. Can someone  
>> look into this problem?
>>
>> I found 6 places with unique="true" in trunk as below. I simply  
>> changed "true" into "false", then started from creating a new  
>> database.
>>
>> accounting\entitydef\entitymodel.xml
>> 1,931: 
>>
>> marketing\entitydef\entitymodel.xml
>> 216: 
>>
>> party\entitydef\entitymodel.xml (2 matches)
>> 714: 
>> 1,007: 
>>
>> product\entitydef\entitymodel.xml (2 matches)
>> 1,839: 
>> 1,842: 
>>
>> I found demo data doesn't specify value for some of these fields,  
>> default value of them is null. When inserting multiple records of  
>> data, demo data seeding will get failure due to the unique index  
>> constrain.
>>
>> Thanks.
>> Weixue Zhang
>>
>>
>>
>> 发件人: Abhijeet Pandey
>> 发送时间: 2009-08-27  16:03:30
>> 收件人: user
>> 抄送: weixuezhang; Abhijeet Pandey
>> 主题: Re: problem Running with MS-SQL
>>
>> Hi Zhang,
>>
>> Thanks for this.
>>
>> Can you guide me that if i need to change all "unique=false" in all  
>> the entitymodel.xml (there are about 26 of them)?
>>
>> Hi All,
>>
>>
>> Does anyone have an idea that why it happens with MSSQL ?
>>
>> Thanks ,
>>
>> Abhijeet Pandey
>>
>>
>>
>> On Sun, Aug 16, 2009 at 4:16 PM, Weixue Zhang > > wrote:
>>
>>
>> I am using ms sql server 2005 and this problem had bothered me for  
>> long time.
>> At last I found it was caused by a few unique indices of some  
>> tables (You
>> can find them by searching with "unique="true"" in files  
>> entitymodel.xml).
>> After I changed them into "unique=false", demo data works fine. Can  
>> anybody
>> explain why this problem doesn't exist with other database servers,  
>> and why
>> we need to set unique=true at some indices while most others are
>> unique=false?
>>
>> Weixue Zhang
>> --
>> View this message in context: 
>> http://www.nabble.com/problem-Running-with-MS-SQL-tp24895969p24992345.html
>>
>> Sent from the OFBiz - User mailing list archive at Nabble.com.
>>
>>
>>
>>
>>
>> -- 
>> Abhijeet Pandey
>



Re: problem Running with MS-SQL

2009-08-30 Thread David E Jones


This sounds like one of those MS-SQL quirks with unique indexes where  
it only allows one row with each possible value, including null. In  
other words, there can only be one record with a null value in that  
column. If I remember right this has come up before too...


There may be a way to change the ALTER statement that adds the index  
to tell it to not include null. It would be nice if that was the  
default since the whole notion is silly, but that's just my subjective  
opinion and obviously theirs is different.


-David


On Aug 30, 2009, at 8:00 PM, Scott Gray wrote:


Hi Weixue,

Could you point me to an example of where the demo data violates a  
unique constraint?


Thanks
Scott

HotWax Media
http://www.hotwaxmedia.com

On 31/08/2009, at 12:12 PM, weixuezhang wrote:

Either demo data or entitymodel definition has problem. Can someone  
look into this problem?


I found 6 places with unique="true" in trunk as below. I simply  
changed "true" into "false", then started from creating a new  
database.


accounting\entitydef\entitymodel.xml
1,931: 

marketing\entitydef\entitymodel.xml
216: 

party\entitydef\entitymodel.xml (2 matches)
714: 
1,007: 

product\entitydef\entitymodel.xml (2 matches)
1,839: 
1,842: 

I found demo data doesn't specify value for some of these fields,  
default value of them is null. When inserting multiple records of  
data, demo data seeding will get failure due to the unique index  
constrain.


Thanks.
Weixue Zhang



发件人: Abhijeet Pandey
发送时间: 2009-08-27  16:03:30
收件人: user
抄送: weixuezhang; Abhijeet Pandey
主题: Re: problem Running with MS-SQL

Hi Zhang,

Thanks for this.

Can you guide me that if i need to change all "unique=false" in all  
the entitymodel.xml (there are about 26 of them)?


Hi All,


Does anyone have an idea that why it happens with MSSQL ?

Thanks ,

Abhijeet Pandey



On Sun, Aug 16, 2009 at 4:16 PM, Weixue Zhang > wrote:



I am using ms sql server 2005 and this problem had bothered me for  
long time.
At last I found it was caused by a few unique indices of some  
tables (You
can find them by searching with "unique="true"" in files  
entitymodel.xml).
After I changed them into "unique=false", demo data works fine. Can  
anybody
explain why this problem doesn't exist with other database servers,  
and why

we need to set unique=true at some indices while most others are
unique=false?

Weixue Zhang
--
View this message in context: 
http://www.nabble.com/problem-Running-with-MS-SQL-tp24895969p24992345.html

Sent from the OFBiz - User mailing list archive at Nabble.com.





--
Abhijeet Pandey






Re: problem Running with MS-SQL

2009-08-30 Thread Scott Gray

Hi Weixue,

Could you point me to an example of where the demo data violates a  
unique constraint?


Thanks
Scott

HotWax Media
http://www.hotwaxmedia.com

On 31/08/2009, at 12:12 PM, weixuezhang wrote:

Either demo data or entitymodel definition has problem. Can someone  
look into this problem?


I found 6 places with unique="true" in trunk as below. I simply  
changed "true" into "false", then started from creating a new  
database.


accounting\entitydef\entitymodel.xml
1,931: 

marketing\entitydef\entitymodel.xml
216: 

party\entitydef\entitymodel.xml (2 matches)
714: 
1,007: 

product\entitydef\entitymodel.xml (2 matches)
1,839: 
1,842: 

I found demo data doesn't specify value for some of these fields,  
default value of them is null. When inserting multiple records of  
data, demo data seeding will get failure due to the unique index  
constrain.


Thanks.
Weixue Zhang



发件人: Abhijeet Pandey
发送时间: 2009-08-27  16:03:30
收件人: user
抄送: weixuezhang; Abhijeet Pandey
主题: Re: problem Running with MS-SQL

Hi Zhang,

Thanks for this.

Can you guide me that if i need to change all "unique=false" in all  
the entitymodel.xml (there are about 26 of them)?


Hi All,


Does anyone have an idea that why it happens with MSSQL ?

Thanks ,

Abhijeet Pandey



On Sun, Aug 16, 2009 at 4:16 PM, Weixue Zhang  
 wrote:



I am using ms sql server 2005 and this problem had bothered me for  
long time.
At last I found it was caused by a few unique indices of some tables  
(You
can find them by searching with "unique="true"" in files  
entitymodel.xml).
After I changed them into "unique=false", demo data works fine. Can  
anybody
explain why this problem doesn't exist with other database servers,  
and why

we need to set unique=true at some indices while most others are
unique=false?

Weixue Zhang
--
View this message in context: 
http://www.nabble.com/problem-Running-with-MS-SQL-tp24895969p24992345.html

Sent from the OFBiz - User mailing list archive at Nabble.com.





--
Abhijeet Pandey




smime.p7s
Description: S/MIME cryptographic signature


Re: Re: problem Running with MS-SQL

2009-08-30 Thread weixuezhang
Either demo data or entitymodel definition has problem. Can someone look into 
this problem?

I found 6 places with unique="true" in trunk as below. I simply changed "true" 
into "false", then started from creating a new database.

accounting\entitydef\entitymodel.xml
1,931:   

marketing\entitydef\entitymodel.xml
216:   

party\entitydef\entitymodel.xml (2 matches)
714:   
1,007:   

product\entitydef\entitymodel.xml (2 matches)
1,839:   
1,842:   

I found demo data doesn't specify value for some of these fields, default value 
of them is null. When inserting multiple records of data, demo data seeding 
will get failure due to the unique index constrain. 

Thanks. 
Weixue Zhang 



发件人: Abhijeet Pandey 
发送时间: 2009-08-27  16:03:30 
收件人: user 
抄送: weixuezhang; Abhijeet Pandey 
主题: Re: problem Running with MS-SQL 
 
Hi Zhang,

Thanks for this.

Can you guide me that if i need to change all "unique=false" in all the 
entitymodel.xml (there are about 26 of them)?

Hi All,


Does anyone have an idea that why it happens with MSSQL ?

Thanks ,

Abhijeet Pandey



On Sun, Aug 16, 2009 at 4:16 PM, Weixue Zhang  wrote:


I am using ms sql server 2005 and this problem had bothered me for long time.
At last I found it was caused by a few unique indices of some tables (You
can find them by searching with "unique="true"" in files entitymodel.xml).
After I changed them into "unique=false", demo data works fine. Can anybody
explain why this problem doesn't exist with other database servers, and why
we need to set unique=true at some indices while most others are
unique=false?

Weixue Zhang
--
View this message in context: 
http://www.nabble.com/problem-Running-with-MS-SQL-tp24895969p24992345.html

Sent from the OFBiz - User mailing list archive at Nabble.com.





-- 
Abhijeet Pandey


Re: problem Running with MS-SQL

2009-08-27 Thread Abhijeet Pandey
Hi,

Does anybody who have implemented ofbiz with MSSQL can guide me please?

Thanks,

Abhijeet Pandey

On Thu, Aug 27, 2009 at 1:33 PM, Abhijeet Pandey
wrote:

> *Hi Zhang,
>
> Thanks for this.
>
> Can you guide me that if i need to change all "unique=false" in all the
> entitymodel.xml (there are about 26 of them)?
>
> Hi All,
>
>
> Does anyone have an idea that why it happens with MSSQL ?
>
> Thanks ,
>
> Abhijeet Pandey
> *
>
>
> On Sun, Aug 16, 2009 at 4:16 PM, Weixue Zhang wrote:
>
>>
>> I am using ms sql server 2005 and this problem had bothered me for long
>> time.
>> At last I found it was caused by a few unique indices of some tables (You
>> can find them by searching with "unique="true"" in files entitymodel.xml).
>> After I changed them into "unique=false", demo data works fine. Can
>> anybody
>> explain why this problem doesn't exist with other database servers, and
>> why
>> we need to set unique=true at some indices while most others are
>> unique=false?
>>
>> Weixue Zhang
>> --
>> View this message in context:
>> http://www.nabble.com/problem-Running-with-MS-SQL-tp24895969p24992345.html
>> Sent from the OFBiz - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Abhijeet Pandey
>



-- 
Abhijeet Pandey


Re: problem Running with MS-SQL

2009-08-27 Thread Abhijeet Pandey
*Hi Zhang,

Thanks for this.

Can you guide me that if i need to change all "unique=false" in all the
entitymodel.xml (there are about 26 of them)?

Hi All,


Does anyone have an idea that why it happens with MSSQL ?

Thanks ,

Abhijeet Pandey
*

On Sun, Aug 16, 2009 at 4:16 PM, Weixue Zhang wrote:

>
> I am using ms sql server 2005 and this problem had bothered me for long
> time.
> At last I found it was caused by a few unique indices of some tables (You
> can find them by searching with "unique="true"" in files entitymodel.xml).
> After I changed them into "unique=false", demo data works fine. Can anybody
> explain why this problem doesn't exist with other database servers, and why
> we need to set unique=true at some indices while most others are
> unique=false?
>
> Weixue Zhang
> --
> View this message in context:
> http://www.nabble.com/problem-Running-with-MS-SQL-tp24895969p24992345.html
> Sent from the OFBiz - User mailing list archive at Nabble.com.
>
>


-- 
Abhijeet Pandey


Re: problem Running with MS-SQL

2009-08-17 Thread snowc

Actually, I think I had a similar problem:

http://www.nabble.com/Violation-of-PRIMARY-KEY-constraint-%27PK_SERVER_HIT%27.-Cannot-insert-duplicate-key-in-object-%27ofbiz.SERVER_HIT%27-tp23479493p23479493.html


Weixue Zhang wrote:
> 
> I am using ms sql server 2005 and this problem had bothered me for long
> time. At last I found it was caused by a few unique indices of some tables
> (You can find them by searching with "unique="true"" in files
> entitymodel.xml). After I changed them into "unique=false", demo data
> works fine. Can anybody explain why this problem doesn't exist with other
> database servers, and why we need to set unique=true at some indices while
> most others are unique=false?
> 

-- 
View this message in context: 
http://www.nabble.com/problem-Running-with-MS-SQL-tp24895969p25019038.html
Sent from the OFBiz - User mailing list archive at Nabble.com.



Re: problem Running with MS-SQL

2009-08-16 Thread Weixue Zhang

I am using ms sql server 2005 and this problem had bothered me for long time.
At last I found it was caused by a few unique indices of some tables (You
can find them by searching with "unique="true"" in files entitymodel.xml).
After I changed them into "unique=false", demo data works fine. Can anybody
explain why this problem doesn't exist with other database servers, and why
we need to set unique=true at some indices while most others are
unique=false?

Weixue Zhang
-- 
View this message in context: 
http://www.nabble.com/problem-Running-with-MS-SQL-tp24895969p24992345.html
Sent from the OFBiz - User mailing list archive at Nabble.com.



RE: problem Running with MS-SQL

2009-08-10 Thread SELC Sales Div

Hi Abhijeet Pandey,

If you are using the default (derby) datasource,
the demo data is OK...it means your OFBiz is OK.

Now, you are moving to change into mssql, then
the loading data fails. There must be something
here

I have not tried using MSSQL in OFbiz, yet; but
what I am going to do is to check if the loaded JDBC driver
is suitable for my MSSQL version which is being used.

Maybe, this can help

- Charles TJ

==


-Original Message-
From: Abhijeet Pandey [mailto:abhijeet.pan...@gmail.com]
Sent: 11 Agustus 2009 12:12
To: user@ofbiz.apache.org
Subject: Re: problem Running with MS-SQL


Hi,

Does anyone has clue , what i should do ?
Or where i can post this, Does anyone has done this before , ie, running
ofbiz on MSSQL ?

Plz guide me.

Thanks,

Abhijeet Pandey





Re: problem Running with MS-SQL

2009-08-10 Thread Carsten Schinzer
I am surprised to see INSERT statements when all you claim doing is to
connect to

   - http://localhost:8080/ecommerce

Just for clarity: You wrote

> The server gets started and i see
> > http://127.0.0.1:8080/ecommerce/control/main
>
> with No Product Store and No promotion category.

> But the database is created. What is the issue.

So I expected the part of the logfile where:

   - your server is started up
   - your attempt to call the above URL is a couple of seconds ago

In order to see where the database queries to get all the store entities
tree are failing.

Can you re-check or simply redo the http request and then take the last
lines from the logfile?
Regards


Carsten


Re: problem Running with MS-SQL

2009-08-10 Thread Carsten Schinzer
Hey Abhijeet,


Can you please check your logfile? There should be some indication in there
...
Regards


Carsten



2009/8/10 Abhijeet Pandey 

> >
> > Hi,
> > I am still stuck at this point.
> > What i explained in my earlier mail that i am able to load demo data with
> > default database.
> > but when i am trying with mssql , DB is created but demo data is not
> loaded
> > because of error which i sent in log.
> > I created fresh DB even though it is giving same problem.
> > Below i have explained what changes i made for switching to MSSQL from
> > derby.
>
> The server gets started and i see
> > http://127.0.0.1:8080/ecommerce/control/main
>
> with No Product Store and No promotion category.
>
> But the database is created. What is the issue.
>
>