OK, I hope it has been fixed. However, what would be interesting to know is
whether you (because it works for you) see the schema name in the queries with
SQL=debug?
I just see:
SELECT LIMIT 0 1 t0.ID, t0.CODE_TYPE_ID, t0.CONTENT, t0.OWNER_ID, t0.TITLE FROM
CODE t0 ORDER BY 1
and I assume you see:
.... MYSCHEMA.CODE t0 .....
Is that right?
I'll post the config I'm using next.
thanks
Adam
Prashant Bhat on 09/01/08 03:17, wrote:
> Hi Adam,
>
> Today, I built the latest snapshot(rev. 609825) and without any
> changes it's working, although the above 'remove' line is still
> present. So I think, it's been corrected already in another part of
> the code:-)
>
> As the Runtime.Trace is displaying the schema property, it's
> configured properly. So a dumb question: are you sure that the
> database contains the schema? because afaik, the mapping tool doesn't
> create the schema.
>
> If you post your complete openjpa configurations, I can try it in my
> sample project here.
>
> Regards,
> Prashant
>
> On Jan 9, 2008 1:45 AM, Adam Hardy <adam.sql@cyberspaceroad.org> wrote:
>> Hi Prashant,
>>
>> do you mind me asking exactly what you patched? I thought I'd patched it - I did
>> this at line 666 but it had no effect:
>>
>>
>> Map.Entry entry;
>> for (Iterator itr = remaining.entrySet().iterator(); itr.hasNext();) {
>> entry = (Map.Entry) itr.next();
>> Object key = entry.getKey();
>> if (key != null) {
>> warnInvalidProperty((String) key);
>> // map.remove(key); // LEAVE openjpa.jdbc.Schema
>>
>> }
>> }
>>
>
|