master branch is the 1.x release (for Rails 2.3 and older), rails3 branch is 
for 2.x release (for, yup, you guessed it, Rails 3.x).

Will try to get a new gem out soon - but things are a little hectic right now.

-- 
Pat

On 28/10/2011, at 6:51 PM, hydrozen wrote:

> The gem is built from the master branch I assume? When can we expect
> those fixes to be published in the gem?
> 
> On Oct 27, 11:27 pm, Pat Allan <[email protected]> wrote:
>> Great :)
>> 
>> On 27/10/2011, at 11:26 PM, hydrozen wrote:
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> At first glance it seems that it might be doing the trick! Did not
>>> test much yet, but I don't get the warning anymore. Will keep you
>>> posted.
>> 
>>> On Oct 24, 1:55 am, Pat Allan <[email protected]> wrote:
>>>> Hi Pat
>> 
>>>> I'm not sure if it's related, but I just merged a patch for STI changes 
>>>> yesterday - can you try using the latest in the rails3 branch via Github, 
>>>> instead of the 2.0.9 gem?
>> 
>>>> Cheers
>> 
>>>> --
>>>> Pat
>> 
>>>> On 21/10/2011, at 6:39 PM, hydrozen wrote:
>> 
>>>>> Hi,
>> 
>>>>> I'm upgrading an application to Ruby 1.9.2 and from Rails 3.0.0 to
>>>>> Rails 3.0.10. I seem to be having an issue with a model that uses STI.
>>>>> The first time the model is used, I get this :
>> 
>>>>> Warning: Error loading /app/models/api/professionnal.rb:
>>>>> Expected /app/models/api/professionnal.rb to define Api::Professionnal
>> 
>>>>> I get the message from the console also if i do
>>>>> Api::Professionnal.first. Api::Professionnal inherits from
>>>>> Api::Profile which defines some indexes. What's weird is that if I do
>>>>> Api::Profile.first and then Api::Professionnal.first, then I don't get
>>>>> any warnings/errors.
>> 
>>>>> Any ideas how to solve this? Can I just ignore this or it probably
>>>>> hides a greater issue?
>> 
>>>>> See this gist for the models and the strack 
>>>>> trace.https://gist.github.com/1304113
>> 
>>>>> Thanks
>> 
>>>>> --
>>>>> You received this message because you are subscribed to the Google Groups 
>>>>> "Thinking Sphinx" group.
>>>>> To post to this group, send email to [email protected].
>>>>> To unsubscribe from this group, send email to 
>>>>> [email protected].
>>>>> For more options, visit this group 
>>>>> athttp://groups.google.com/group/thinking-sphinx?hl=en.
>> 
>>> --
>>> You received this message because you are subscribed to the Google Groups 
>>> "Thinking Sphinx" group.
>>> To post to this group, send email to [email protected].
>>> To unsubscribe from this group, send email to 
>>> [email protected].
>>> For more options, visit this group 
>>> athttp://groups.google.com/group/thinking-sphinx?hl=en.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Thinking Sphinx" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/thinking-sphinx?hl=en.
> 

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

Reply via email to