Support for multiple databases

298 views
Skip to first unread message

May Lwin

unread,
Nov 25, 2011, 3:53:01 AM11/25/11
to play-fr...@googlegroups.com
Dear play framework developers,

We are currently using play 1.2.4-RC2. Our application needs to connect to multiple databases with different schema. The documentation for multiple databases support here (http://www.playframework.org/documentation/1.2.3/model#multiple) suggests to use "Connection conn = DB.getDBConfig(configName).getConnection();". However when I checked play.db.DB class, there was no such method and not even similar methods for multiple db support. Could you kindly suggest whether I missed out something or I used different play version? I do appreciate your suggestion in advance.

Best regards,
may

GrailsDeveloper

unread,
Nov 25, 2011, 8:37:29 AM11/25/11
to play-framework
As far as I know multidb-support is only part of the 1.3 branch.
Niels

Dominik Dorn

unread,
Nov 27, 2011, 12:31:06 PM11/27/11
to play-fr...@googlegroups.com
you could use ebean instead of jpa, which comes with multi-db support
out of the box.

> --
> You received this message because you are subscribed to the Google Groups "play-framework" group.
> To post to this group, send email to play-fr...@googlegroups.com.
> To unsubscribe from this group, send email to play-framewor...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/play-framework?hl=en.
>
>

--
Dominik Dorn
http://dominikdorn.com
http://twitter.com/domdorn

Skripten, Mitschriften, Lernunterlagen, etc. findest Du auf
http://www.studyguru.eu !

Nicolas Leroux

unread,
Nov 27, 2011, 2:59:05 PM11/27/11
to play-fr...@googlegroups.com
Multi db is not part of the 1.2.x series. I guess there is a mistake with the documentation. Could you open a bug? 

Thanks

Nicolas

May Lwin

unread,
Nov 27, 2011, 8:26:43 PM11/27/11
to play-fr...@googlegroups.com
If it is that so, multiple db support is available in 1.2.x series. we would like to know if there is an alternative? Many thanks for your information. I already reported this documentation mistake as a bug.

Best regards,
may
Reply all
Reply to author
Forward
0 new messages