Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm currently a developer of Siena but not since very long. Let me explain why I became a developer on this project? I went to Siena because I wanted to use Play+GAE and Siena appeared to be a good start for GAE DB and I really wanted to avoid JDO/JPA. Then, I began to really appreciate Siena for its straightforward, light and easy approach and so simple APIs. It doesn't pretend to be the all-in-one abstraction layer like JDO and the greatest standard DB API like JPA. It really made me think of DB APIs from Python/Ruby and it really fits my point of view: I want a simple DB API which allows me to solve the great majority of my problems and when I have a more complex problem, I will use the lower layer APIs but certainly not an abstraction layer such as hibernate.</p> <p>The possibility to make my code work on GAE DB or JDBC was also a good aspect. Once again, Siena doesn't pretend to provide exactly the same things in both worlds because SQL and NoSQL are not really compatible (but ORM is neither really compliant to SQL model :) ). But once again, it is quite practical to be able to rely on the same APIs in several DBs.</p> <p>Finally, the library is ONE jar and you don't have to retrieve the whole universe to use it. </p> <p>So, I became progressively a committer on Siena because I wanted to take part of this nice little adventure. Now siena team is working on a new version keeping the same simple APIs, bringing new interesting features and really improving all the backend code to make it even easier to extend for new DB support. Siena is a pragmatic API driven by user experiences and that's why I like it ;)</p> <p>Pascal</p>
    singulars
    1. This table or related slice is empty.
    1. POHow mature is Ebean or Siena?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USmandubian
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for sharing your experience, even if it doesn't show how mature it is. What I don't understand is why I can't switch between GAE and JDBC? I thought this was the great benefit of Siena. I mean otherwise it looks more clever to use specific "ORM-Mapper".
      singulars
      1. PO
      1. USniels
    2. COI never told that you can't switch between GAE and JDBC with Siena :D... You CAN switch and as you said, this is one of the great benefit of Siena. But we don't say you can ALWAYS switch between both because everything is not possible between SQL and NoSQL. Sometimes, you must design your models specifically for NoSQL or for SQL to be efficient... We don't pretend to solve all the problems between NoSQL and SQL because it would be a lie. But in the great majority of cases, the switch will work without any problem.
      singulars
      1. PO
      1. USmandubian
    3. COConcerning the maturity, I'm not really the right person as I'm coding for Siena for the time being :)... But I know people use it in production and they chose Siena against JDO/JPA or other stuff in order to have a very simple API with a thin layer between their code and the DB... What's sure is that the code is very small, you only need one jar and the learning curve is very short... We are currently cleaning the code/design very carefully and implementing lots of tests so I think the quality of Siena will grow and grow... Don't hesitate to talk directly to siena group if you need anything!
      singulars
      1. PO
      1. USmandubian
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload