Running SQL against legacy database.

[snowch]

I have a legacy database that until now I have been just using read-only.  I now have a need to update some fields.  What are my options?

I have been using entities with 'no-auto-stamp="true"' mentioned, but I am not sure what it does.  Can anyone on this forum explain?

Alternatively, can I run SQL statements directly from my services to perform these small db updates?

Many thanks in advance,

Chris

[Adrian Crum]

You have to set no-auto-stamp="true" on your legacy database because it
doesn't contain the necessary fields.

You can use your legacy database the same as any OFBiz entity. There is
nothing special to do.

Why do you need to run SQL directly? Is there something missing in the
entity engine that you need?

-Adrian

snowch wrote:

> I have a legacy database that until now I have been just using read-only.  I
> now have a need to update some fields.  What are my options?
>
> I have been using entities with 'no-auto-stamp="true"' mentioned, but I am
> not sure what it does.  Can anyone on this forum explain?
>
> Alternatively, can I run SQL statements directly from my services to perform
> these small db updates?
>
> Many thanks in advance,
>
> Chris

[snowch]

Hi Adrian,

I wasn't sure if the entity engine would function properly with no-auto-stamp="true".  I thought the auto-stamp fields may be required for versioning of the data.

If the entity engine works ok read/write with no-auto-stamp="true", then I will do my updates using entitites.

Many thanks,

Chris

Adrian Crum wrote

You have to set no-auto-stamp="true" on your legacy database because it
doesn't contain the necessary fields.

You can use your legacy database the same as any OFBiz entity. There is
nothing special to do.

Why do you need to run SQL directly? Is there something missing in the
entity engine that you need?

-Adrian

snowch wrote:
> I have a legacy database that until now I have been just using read-only.  I
> now have a need to update some fields.  What are my options?
>
> I have been using entities with 'no-auto-stamp="true"' mentioned, but I am
> not sure what it does.  Can anyone on this forum explain?
>
> Alternatively, can I run SQL statements directly from my services to perform
> these small db updates?
>
> Many thanks in advance,
>
> Chris

[Jacques Le Roux]

auto-stamp is mostly (if not only) used for synchronization between DBs.

Jacques

From: "snowch" <[hidden email]>

>
> Hi Adrian,
>
> I wasn't sure if the entity engine would function properly with
> no-auto-stamp="true".  I thought the auto-stamp fields may be required for
> versioning of the data.
>
> If the entity engine works ok read/write with no-auto-stamp="true", then I
> will do my updates using entitites.
>
> Many thanks,
>
> Chris
>
>
> Adrian Crum wrote:
>>
>> You have to set no-auto-stamp="true" on your legacy database because it
>> doesn't contain the necessary fields.
>>
>> You can use your legacy database the same as any OFBiz entity. There is
>> nothing special to do.
>>
>> Why do you need to run SQL directly? Is there something missing in the
>> entity engine that you need?
>>
>> -Adrian
>>
>> snowch wrote:
>>> I have a legacy database that until now I have been just using read-only.
>>> I
>>> now have a need to update some fields.  What are my options?
>>>
>>> I have been using entities with 'no-auto-stamp="true"' mentioned, but I
>>> am
>>> not sure what it does.  Can anyone on this forum explain?
>>>
>>> Alternatively, can I run SQL statements directly from my services to
>>> perform
>>> these small db updates?
>>>
>>> Many thanks in advance,
>>>
>>> Chris
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Running-SQL-against-legacy-database.-tp23278522p23279182.html
> Sent from the OFBiz - User mailing list archive at Nabble.com.
>