Hi Alan I'm unclear as to how your code might be broken based on the 1.6.4 release. In terms of query results, there were some internal optimisations that were carried out to improve performance but nothing should have changed in the public API. If you can be clearer on what you perceive has changed, I can either clarify correct usage or add a bug to be fixed.
Version 1.6.3 has not been removed either, as per standard pip usage, you can install that specific version by using: pip install py2neo==1.6.3 Nigel On 21 March 2014 22:32, Alan Robertson <al...@unix.sh> wrote: > Hi Nigel, > > When you return query results, you've had 3 different versions of how to > introspect the column names of the resulting data (1.6.4 being the > latest one). > > Could you *please* create a consistent method for me to use to extract > the column names and then keep that working on your new versions? > [Having it be an object method would be awesome]. > > I really need to know the column names so I can create corresponding > columns with Python objects of the same names as the Neo4j objects you > deliver to me. > > If you could do this, it would be very helpful for me, and would > eliminate the last two reasons I got extremely frustrated with py2neo. > > Of course, this is made more frustrating by the fact that 1.6.3 is not > longer available. > > If you feel the need to break APIs, it would be good to allow the old > version to stay around for those who haven't converted to the new > version yet. > > > -- > Alan Robertson <al...@unix.sh> - @OSSAlanR > > "Openness is the foundation and preservative of friendship... Let me > claim from you at all times your undisguised opinions." - William > Wilberforce > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to neo4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
