I do not see anything, I will probably just stick with manual CSV or XML transfers. I was thinking of using it to load all the current data and later to pull down data for report generation, but I am sure I can figure out alternatives. If a real need arises I can setup some sort of automated procedure to generate and transfer the CSV or XML files.
On Aug 12, 1:10 am, Robert Kluin <robert.kl...@gmail.com> wrote: > Hey Joshua, > I'm not at all familiar with that tool, but i'd guess unless you can > find some type of adapter someone else has written you'll probably > need to write something. Maybe Pentaho can use REST services (or some > other service) which would make your life easier. ;) > > Robert > > > > > > > > On Thu, Aug 11, 2011 at 11:20, Joshua Mulloy <jmul...@sau4.org> wrote: > > Hey Robert, > > > You had asked if I had a particular ETL tool in mind. I use Pentaho > > Data Integration which used to be known as KETTLE for moving data > > around. I connects to all sorts of databases and makes transformation > > of data a snap. I haven't figured out how to connect it to a Google > > App Datastore instance but I will keep looking and post back if I find > > a way. > > > On Aug 11, 12:41 am, Robert Kluin <robert.kl...@gmail.com> wrote: > >> Hi Joshua, > >> Responses inline. > > >> On Wed, Aug 10, 2011 at 16:11, Joshua Mulloy <jmul...@sau4.org> wrote: > >> > I definitely agree with you on the python vs c markup. > >> > I just came back to post on my progress and read your post. After > >> > reading > >> > your post, I am not sure I made the right decision (actually using more > >> > of > >> > the Django framework). You sound very opposed to Django. If you are > >> > willing to share, I would be very interested in your reasons. I found > > >> I'm not necessarily personally opposed to it, but it carries overhead > >> which does not always play well on app engine. It is also very heavy > >> and I find it rather monolithic. I personally prefer lighter, smaller > >> frameworks. > > >> > Django-nonrel and two things made me decide to use the model framework. > >> > First, I really liked the Model syntax. I think it was easier for me to > >> > understand because they provided the related SQL code in their > >> > book http://www.djangobook.com/en/2.0/chapter05/. I was very frustrated > >> > by > >> > the lack of comparison examples in Programming Google App Engine. For > >> > example, instead of just mentioning (page 197) "This technique is > >> > similar to > >> > how you'd use 'join tables' in an SQL database." an actual mapped example > >> > would probably have made that entire chapter immediately mentally > >> > digestible. > > >> The problem with App Engine is that you'll get into trouble by > >> thinking in terms of SQL. It is not SQL, and your *really* should try > >> to not think in SQL-like terms. Instead think simple data structures > >> and denormalize the hell out of stuff, precisely the opposite of > >> typical RDMS thinking. > > >> > Second, I like that I can take the code and plop it somewhere else if > >> > necessary. I got burned from an unexpected limitation in GAS. If I run > >> > into another road block with GAE, I can take my code and run it on my > >> > server > >> > here with minor adjustment to the code. > > >> Yeah, that is a bummer. Luckily most of your code will probably be > >> pretty portable no matter what you choose, worst case you might need > >> to implement a thin datastore abstraction layer. Or you could use > >> TyphoonAE! > > >> > I have basically setup the data model for my app and the Django admin > >> > interface already has at least as much functionality as the old app. In > >> > looking at it, I could probably just put that up and give out one login > >> > and > >> > volunteers could start entering data (basically what they had before but > >> > needed a client). Then I could start "adding" features like: > >> > users inputting their own data instead of volunteers copying it from a > >> > paper > >> > form. There is still a ton I need to do and better understand. But > >> > now, I > >> > at least have an interface I can show to the PD committee and my boss and > >> > that is a big relief. I now have a bit more time to plan and consider > >> > alternatives, time I didn't think I would have this morning. > > >> Honestly, I can't argue with results. > > >> Nice to hear you chose Python. :) > > >> Robert > > >> > -- > >> > You received this message because you are subscribed to the Google Groups > >> > "Google App Engine" group. > >> > To view this discussion on the web visit > >> >https://groups.google.com/d/msg/google-appengine/-/IyyYM6sSoHcJ. > >> > To post to this group, send email to google-appengine@googlegroups.com. > >> > To unsubscribe from this group, send email to > >> > google-appengine+unsubscr...@googlegroups.com. > >> > For more options, visit this group at > >> >http://groups.google.com/group/google-appengine?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To post to this group, send email to google-appengine@googlegroups.com. > > To unsubscribe from this group, send email to > > google-appengine+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
