A further update: moving a specific text column from the old table seems to
cause the LOB data to be present on the new table. The specific text column
holds callstack values.
On Wed, 27 Mar 2019 at 15:34, Tom P wrote:
> Still problematic and with LOB data.
>
> I ran another test and by not
Still problematic and with LOB data.
I ran another test and by not copying the text values from the old table to
the new it successfully works and no LOB data. Including the text columns
from the old table in the copy seems to be where the problem is. I even
tried casting during the move but no
Same result unfortunately
Cheers
On Wed, 27 Mar 2019 at 12:54, wrote:
> Can you change the object names in the script below and see if it returns
> the same results on that system? (At least to isolate something
> system-related as a starting point)
>
>
>
> Regards,
>
>
>
> Greg
>
>
>
> Dr
Can you change the object names in the script below and see if it returns the
same results on that system? (At least to isolate something system-related as a
starting point)
Regards,
Greg
Dr Greg Low
1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax
Hi Greg
When I run this on my local Sql install and insert dummy data all works as
expected like you. However on the actual server when I MOVE the data from
the original table to the new one then the problems comes up and the new
table has LOB_DATA.
I am not sure where to go from here. Any
Some call APIs but the vast majority are just mapping calls. Changing one
object into another.
Davy
On Tue, 26 Mar 2019, 21:51 Greg Keogh, wrote:
>
> This is pretty typical for the entire project.
>> var legalEntity = await CreateLegalEntityObjectAsync(...);
>> var billingAccount =
> This is pretty typical for the entire project.
> var legalEntity = await CreateLegalEntityObjectAsync(...);
> var billingAccount = await CreateBillingAccountObjectAsync(...);
>
But what's inside all the awaited methods? Are they actually doing anything
asynchronously (web service calls,
Yes David, there are whole chains of method calls, all awaiting for
something to complete, the only part that is not async is the database call!
*... .. / --- -.-. / .-.. . --. . .-. . / ... -.-. .. ... / -. .. --
.. ..- -- / . .-. ..- -.. .. - .. --- -. .. ... / .- -... . ... .-.-.-*
Presumably inside these methods are other calls to additional async
methods?
This sounds like an example of how "viral" the async/await stuff can be, in
that once you call an async method at the lowest level, everything further
up ends up needing to become "async/awaited" too.
David
On Tue, 26
Hi Greg,
This is pretty typical for the entire project.
var legalEntity = await CreateLegalEntityObjectAsync(...);
var billingAccount = await CreateBillingAccountObjectAsync(...);
var billingAccountUid = billingAccount.UserName;
var billingAccountTaxServiceAddressPcode =
*forking* hell!
regards,
Preet, in Auckland NZ
On Tue, 26 Mar 2019 at 22:52, Greg Keogh wrote:
>
> I've started a new post, and one of the applications here uses Async Await
>> for nearly every method call, even for simple calls that just create an
>> object and return it.
>>
>
> How on
> I've started a new post, and one of the applications here uses Async Await
> for nearly every method call, even for simple calls that just create an
> object and return it.
>
How on earth is that sort of thing coded? How are intrinsically synchronous
methods forcibly turned into async ones? Is
Hello all,
I've started a new post, and one of the applications here uses Async Await
for nearly every method call, even for simple calls that just create an
object and return it.
Are there any pitfalls for using this many await methods in an application?
Davy.
*... .. / --- -.-. / .-..
13 matches
Mail list logo