Re: [BangPypers] Feb meetup

2013-02-11 Thread Jonathan Toomim
I can give a quick talk on my HEG/near-infrared spectroscopy work. On 2/8/2013 4:54 PM, kracekumar ramaraju wrote: All, Feb Meetup will be on 16th, as usual 3.00 PM, shall we have meetup in CIS or for other place, do suggest, Feel free to propose lighting talk/30 mins talk. _

Re: [BangPypers] Feb meetup

2013-02-11 Thread Kracekumar Ramaraju
Hope there are uses of python in the project. On Mon, Feb 11, 2013 at 5:55 PM, Jonathan Toomim wrote: > I can give a quick talk on my HEG/near-infrared spectroscopy work. > > > On 2/8/2013 4:54 PM, kracekumar ramaraju wrote: > >> All, >> >> Feb Meetup will be on 16th, as usual 3.00 PM, shall we h

Re: [BangPypers] Feb meetup

2013-02-11 Thread Jonathan Toomim
The software I wrote to give people realtime feedback on their brain state is open source and 100% Python. On 2/11/2013 9:29 PM, Kracekumar Ramaraju wrote: Hope there are uses of python in the project. On Mon, Feb 11, 2013 at 5:55 PM, Jonathan Toomim wrote: I can give a quick talk on my HEG/

Re: [BangPypers] SQLAlchemy and 'non-trivial' default values for a column

2013-02-11 Thread Sriram Karra
On Wed, Feb 6, 2013 at 12:05 PM, Dhruv Baldawa wrote: > OK I misread. Let me see if I understood your problem correctly. > >1. All the consultations will be stored in that table. >2. When you have a Consultation object, you need a `consultation_count` >property for the number of consul

Re: [BangPypers] SQLAlchemy and 'non-trivial' default values for a column

2013-02-11 Thread Sriram Karra
On Wed, Feb 6, 2013 at 1:37 PM, Thava Alagu wrote: > Hi Karra, > > > Since you want more flexible system, I recommend that you add more > columns-- > apt date, reservation date, actual visit date and *time* of consultation. > I have some of those fields, but did not show them in my mail in the i

Re: [BangPypers] SQLAlchemy and 'non-trivial' default values for a column

2013-02-11 Thread Dhruv Baldawa
-- Dhruv Baldawa (http://www.dhruvb.com) On Tue, Feb 12, 2013 at 7:13 AM, Sriram Karra wrote: > On Wed, Feb 6, 2013 at 12:05 PM, Dhruv Baldawa >wrote: > > > OK I misread. Let me see if I understood your problem correctly. > > > >1. All the consultations will be stored in that table. > >

Re: [BangPypers] SQLAlchemy and 'non-trivial' default values for a column

2013-02-11 Thread Sriram Karra
On Tue, Feb 12, 2013 at 9:08 AM, Dhruv Baldawa wrote: > > Yes, this will be consistent. Just to explain in brief how it works. The > default function gets executed in runtime, when a new record is created, it > just go throughs the database, finds the number of records for that > particular date a

Re: [BangPypers] SQLAlchemy and 'non-trivial' default values for a column

2013-02-11 Thread Dhruv Baldawa
try session.query(Consultation).filter_by(), sorry I am actually used to using the above specified syntax because I usually use Flask-SQLAlchemy. -- Dhruv Baldawa (http://www.dhruvb.com) On Tue, Feb 12, 2013 at 11:35 AM, Sriram Karra wrote: > On Tue, Feb 12, 2013 at 9:08 AM, Dhruv Baldawa >wr

Re: [BangPypers] SQLAlchemy and 'non-trivial' default values for a column

2013-02-11 Thread Sriram Karra
On Tue, Feb 12, 2013 at 11:38 AM, Dhruv Baldawa wrote: > try session.query(Consultation).filter_by(), sorry I am actually used to > using the above specified syntax because I usually use Flask-SQLAlchemy. Oh, well. the session object is not available inside Consultation class. And as I mentioned

Re: [BangPypers] SQLAlchemy and 'non-trivial' default values for a column

2013-02-11 Thread Dhruv Baldawa
Then I guess you are doing it the wrong way. You should only have a single session object (unless working with multiple databases simultaneously). The object should be binded with whatever connection is required. if PRODUCTION: engine = create_engine(...) else: engine = create_engine(...)