Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>When it comes to enterprise ready, I'm not sure how much more ready a stack using Pylons with SQLAlchemy can be in the Python world. You're ready for massive legacy databases with crazy schemas (totally common in large corporate worlds), something where Django just falls apart at the seams. Sure, in Django, you <em>could</em> still use SQLAlchemy, but then all the Django contrib tools fall apart since they all rely on the assumption that you'd doing things the "Django" way.</p> <p>Pylons has been around since mid-2005, and it isn't going anywhere. It's actually quite mature, and has a fairly slow and solid release schedule of 6-10 months between releases, with quite a bit of testing. One of the core Pylons developers is also a developer on Jython ensuring that Pylons can run on the JVM (which helps get Pylons based apps into enterprise environments that are hostile to things that can't be packaged up into a WAR file for deployment).</p> <p>Regarding some of the other 'answers' here, the question is about whether Pylons is enterprise-ready, I have no idea why others were unable to read the question and instead chose to start preaching their own favorite framework. It's quite silly to say that you should use Django/Zope/Grok because it has "bigger uptake" or a "larger community", if that's the criteria the choice should be PHP, which makes the Django and Zope communities look itty bitty in comparison. Pylons definitely has a large enough community to sustain itself, especially as its rather lean and compact code-base don't pick up nearly as many bugs as the "kitchen sink" frameworks of Zope/Django.</p>
    singulars
    1. This table or related slice is empty.
    1. POIs Pylons enterprise-ready?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USBen Bangert
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs Pylons enterprise-ready?
      singulars
      1. PTQuestion
    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. COHello, Ben! I am immensely honored to hear your frank and sensible reply. You have done alot of work for the wonderful framework Pylons and I appreciate it greatly. I am currently VERY interested in Pylons but I am left very anxious about IBM's support for the DB2 driver for SQLAlchemy. It has yet to be updated to SA 0.5 from SA 0.4 when Pylons 0.97 depends on SA 0.5. I concur with your opinions about "bigger uptake" but noting that you claim that Pylons "isn't going anywhere" wouldn't u agree a bigger community will indicate more support?
      singulars
      1. PO
      1. UScygnus atratus
    2. COMoreover, I shifted to Pylons from ROR due to a lack of support for Windows developers and the lackluster ruby-pg driver. It took up quite a lot of my time and caused me to become horribly frustrated. I have to clarify by 'enterprise ready' my main concern is reliability, support for legacy code and longevity. So far, I have been quite happy with Pylons thats why the question. But I do hope IBM will continue SA support for DB2 as well as Python.
      singulars
      1. PO
      1. UScygnus atratus
    3. COWell, for legacy support, Pylons is currently almost 1/3rd legacy support for older versions of Pylons. We didn't "wait" for 1.0 before deciding that early adopters should have legacy support. Pylons 1.0, which is due out in the next 6 months, drops the legacy support, but will also have a Pylons 0.10 released at the same time containing deprecation warnings for a smoother upgrade to 1.0. With regards to support, you'll probably have a more difficult time getting Python DB2 support than Pylons support.
      singulars
      1. PO
      1. USBen Bangert
 

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