[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4426) Filtering Oracle's bogus $BIN tables

[Max Rydahl Andersen (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12474524#action_12474524 ] 

Max Rydahl Andersen commented on JBIDE-4426:
--------------------------------------------

Sorry, I thought you did this on a seam project where such file is created automatically.

You can do it manually and call it whatever you like, i.ek. krasimir.properties and add that metadatadialect line from above.
Then edit your console configuration and point to the file in the Properties field, apply and reload the configuration (to be completely
sure it is picked up restart your eclipse)

Now you should have forced eclipse to use the OracleMetaDataDialect independent of what your db actually is.

If that fixes it we know that the oracle detection code is not working for you, and if it does not fix it we know that the oraclemetadatadialect is broken for you.

> Filtering Oracle's bogus $BIN tables
> ------------------------------------
>
>                 Key: JBIDE-4426
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4426
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Hibernate
>    Affects Versions: 3.1.0.M1
>         Environment: Galileo RC2
> JBTools H235
> DB Oracle 10.2.0.1.0 
>            Reporter: Krasimir Goutcev
>            Assignee: Max Rydahl Andersen
>             Fix For: 3.1.0.M3
>
>         Attachments: 2009-06-04_1050.png, JBIDE-4426_patch.txt
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira