Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I differ from @tereško here - ORMs can make database queries easier to write and easier to maintain. There is some great work going into Propel and Doctrine, in my opinion - take advantage of them! There are a number of performance comparisons on the web, and check out <a href="http://www.notorm.com/" rel="nofollow noreferrer">NotORM</a> as well (I've not used it but they do some comparisons to Doctrine, if I recall correctly).</p> <p><em>If</em> you get to a point where your throughput requires you to do raw SQL then optimise at that point. But in terms of reducing your bug count and increasing your productivity, I think that your savings will fund a better server anyway. Of course, your mileage may vary.</p> <p>I don't know RedBean, incidentally, but I am mildly of the view that Propel is faster than Doctrine in most cases, since the classes are pre-generated. I used Propel when it was the only option and have stuck with it, though I certainly wouldn't be averse to using Doctrine.</p> <h2>2018 update</h2> <p>Propel 2 is still in alpha after a number of years, and is in need of a number of large refactoring projects, which sadly were not getting done. Although the maintainers say that this alpha is good to use in production, since it has good test coverage, they have now started on Propel 3. Unfortunately, this has not actually had any releases yet, at the time of my writing this, despite the repository being a year old.</p> <p>While I think Propel was a great project, I wonder if it is best to use something else for the time being. It could yet rise from the ashes!</p>
    singulars
    1. This table or related slice is empty.
    1. PORedBean ORM performance
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UShalfer
    1. UShalfer
    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. COin case of pulling more than 1000 of records from db using orm does it consume more space? most probably i think the orm output will be in form of array of object.
      singulars
      1. PO
      1. USJaison Justus
    2. COGenerally speaking, you should be wary of holding large numbers of rows in memory regardless of your ORM. That number sounds fine for an offline process, but not for a web request. Instead, you should do it in pieces: do 20 selects of 50 elements each, say; that will keep memory usage down. Or, you could do this part with raw db calls (via an ORM to maintain db independence) if it's a small part of your application. Lastly (and best yet) see if you can move this thing to an offline process.
      singulars
      1. PO
      1. UShalfer
    3. COhmmm nice spark. so you prefer to manage the data access from database in a managed way. and should be managed by us.
      singulars
      1. PO
      1. USJaison Justus
 

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