Michael Bayer wrote:
> Rodney Haynie wrote:
>
>>>
>> Ok, tried it. Still no data being committed.
>> No errors popping either.
>>
>
> its likely a turbogears usage issue so check with their list. I know
> they have their own idea about transactional scope.
>
> For what its
Michael Bayer wrote:
> Rodney Haynie wrote:
>
>>>
>> Ok, tried it. Still no data being committed.
>> No errors popping either.
>>
>
> its likely a turbogears usage issue so check with their list. I know
> they have their own idea about transactional scope.
>
> Ok, will do.
>
Rodney Haynie wrote:
>>
>>
> Ok, tried it. Still no data being committed.
> No errors popping either.
its likely a turbogears usage issue so check with their list. I know
they have their own idea about transactional scope.
--~--~-~--~~~---~--~~
You received th
Michael Bayer wrote:
> Rodney Haynie wrote:
>
>> Michael Bayer wrote:
>>
>>> Rodney Haynie wrote:
>>>
>>>
I am having problems getting my data to save when the changes are made
through stored procedures.
I created a sample block of code below to show exactly how I am
Rodney Haynie wrote:
>
>
> Michael Bayer wrote:
>> Rodney Haynie wrote:
>>
>>> I am having problems getting my data to save when the changes are made
>>> through stored procedures.
>>> I created a sample block of code below to show exactly how I am
>>> implementing this.
>>>
>>>
>>> conn
Michael Bayer wrote:
> Rodney Haynie wrote:
>
>> I am having problems getting my data to save when the changes are made
>> through stored procedures.
>> I created a sample block of code below to show exactly how I am
>> implementing this.
>>
>>
>> conn = DBSession.connection()
>>
Rodney Haynie wrote:
>
> I am having problems getting my data to save when the changes are made
> through stored procedures.
> I created a sample block of code below to show exactly how I am
> implementing this.
>
>
> conn = DBSession.connection()
> statement = sql.text("""CALL in
