Smalltalk › Instantiations

ODBC classes (AbtOdbcVarCharField etc.) excluded in 8.5.1 packaging

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Wayne Johnston

ODBC classes (AbtOdbcVarCharField etc.) excluded in 8.5.1 packaging

Migrating from 7.5.1 to 8.5.1, I hit a problem. An application of ours which uses ODBC blew up at runtime due to several classes in AbtDbmOdbcApp being reduced out. The initial walkback I hit was because many but not all slots in AbtOdbcDatabaseManager's typeDict were nil. Our application is indirectly dependent on AbtDbmOdbcApp so it appears in the list of "Selected Applications and ICs" when packaging. The ugly fix I implemented was to say #doNotReduceClassNamed: for each class I was missing, or actually all that #typeDict references. Should I have had to do this?

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/KOJtzZoDcgYJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

Bob Brodd

Re: ODBC classes (AbtOdbcVarCharField etc.) excluded in 8.5.1 packaging

Hi Wayne,

This is indeed a bug, but has been fixed in the soon to be released 8.5.2, so in 8.5.1, you will need to do something to force the classes into the packaged image. You can stick with what you have done, or insert a snippet of code into your apps initialization code that will trick the packager into including all of the necessary classes:

( false ) ifTrue: [ AbtOdbcDatabaseManager initializeAfterLoad ].

Bob

On Thursday, September 6, 2012 1:05:54 PM UTC-4, Wayne Johnston wrote:

Migrating from 7.5.1 to 8.5.1, I hit a problem. An application of ours which uses ODBC blew up at runtime due to several classes in AbtDbmOdbcApp being reduced out. The initial walkback I hit was because many but not all slots in AbtOdbcDatabaseManager's typeDict were nil. Our application is indirectly dependent on AbtDbmOdbcApp so it appears in the list of "Selected Applications and ICs" when packaging. The ugly fix I implemented was to say #doNotReduceClassNamed: for each class I was missing, or actually all that #typeDict references. Should I have had to do this?

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/QacfUWK1To8J.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.

Dusty-2

Re: ODBC classes (AbtOdbcVarCharField etc.) excluded in 8.5.1 packaging

Back in VAST 5.5 we did 2 things to include odbc.
one was to have aOdBC := AbtOdbcDatabaseManager new, in runtime code.
(ugly, but it was the early 90s...)
the other is in packaging instructions, set the entire AbtDbmOdbcApp
to doNotReduce, which works well.
So far in 8.5 we've not had a problem, but seeing the bug now, we'll
keep a lookout when we go to 8.5.1/8.5.2.

On 9/6/12, Bob Brodd <[hidden email]> wrote:

> Hi Wayne,
>
> This is indeed a bug, but has been fixed in the soon to be released 8.5.2,
> so in 8.5.1, you will need to do something to force the classes into the
> packaged image. You can stick with what you have done, or insert a snippet
>
> of code into your apps initialization code that will trick the packager
> into including all of the necessary classes:
>
> * ( false ) ifTrue: [ AbtOdbcDatabaseManager initializeAfterLoad ].*
> *
> *
> Bob
>
> On Thursday, September 6, 2012 1:05:54 PM UTC-4, Wayne Johnston wrote:
>>
>> Migrating from 7.5.1 to 8.5.1, I hit a problem. An application of ours
>> which uses ODBC blew up at runtime due to several classes in AbtDbmOdbcApp
>>
>> being reduced out. The initial walkback I hit was because many but not
>> all
>> slots in AbtOdbcDatabaseManager's typeDict were nil. Our application is
>> indirectly dependent on AbtDbmOdbcApp so it appears in the list of
>> "Selected Applications and ICs" when packaging. The ugly fix I
>> implemented
>> was to say #doNotReduceClassNamed: for each class I was missing, or
>> actually all that #typeDict references. Should I have had to do this?
>
> --
> You received this message because you are subscribed to the Google Groups
> "VA Smalltalk" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/va-smalltalk/-/QacfUWK1To8J.
> To post to this group, send email to [hidden email].
> To unsubscribe from this group, send email to
> [hidden email].
> For more options, visit this group at
> http://groups.google.com/group/va-smalltalk?hl=en.
>
>

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.