<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for LuckyDonkey</title>
	<atom:link href="http://www.luckydonkey.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.luckydonkey.com</link>
	<description>Never knowingly knowing narwhals</description>
	<lastBuildDate>Sun, 04 Sep 2011 22:12:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>Comment on Mac OSX: starting postgres on boot by Andre</title>
		<link>http://www.luckydonkey.com/2008/07/03/mac-osx-starting-postgres-on-boot/comment-page-1/#comment-3294</link>
		<dc:creator>Andre</dc:creator>
		<pubDate>Sun, 04 Sep 2011 22:12:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.luckydonkey.com/?p=208#comment-3294</guid>
		<description>It works like a charm. Thank you very much. Just one thing: the script only works for starting the service up, not shutting it down or restarting it.

So I would change the bash script bit a little. I&#039;d replace the word start at the end of the line for $1 . That way you can actually using the SystemStarter tool to start and stop the service (e.g., SystemStarter stop PostgreSQL)</description>
		<content:encoded><![CDATA[<p>It works like a charm. Thank you very much. Just one thing: the script only works for starting the service up, not shutting it down or restarting it.</p>
<p>So I would change the bash script bit a little. I&#8217;d replace the word start at the end of the line for $1 . That way you can actually using the SystemStarter tool to start and stop the service (e.g., SystemStarter stop PostgreSQL)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Python Style Plugins Made Easy by Erics Blog</title>
		<link>http://www.luckydonkey.com/2008/01/02/python-style-plugins-made-easy/comment-page-1/#comment-3231</link>
		<dc:creator>Erics Blog</dc:creator>
		<pubDate>Mon, 28 Feb 2011 16:59:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.luckydonkey.com/2008/01/02/python-style-plugins-made-easy/#comment-3231</guid>
		<description>&lt;strong&gt;Vorstellung eines einfachen Plugin Systems für Python...&lt;/strong&gt;

Plugins sind vereinfacht gesagt einzelne Abschnitte eines Programms, die nachträglich in das Hauptprogramm integriert werden. So kann der Funktionsumfang einer Application unkompliziert erweitert werden. Ein populäres Beispiel hierfür sind sicherlich d...</description>
		<content:encoded><![CDATA[<p><strong>Vorstellung eines einfachen Plugin Systems für Python&#8230;</strong></p>
<p>Plugins sind vereinfacht gesagt einzelne Abschnitte eines Programms, die nachträglich in das Hauptprogramm integriert werden. So kann der Funktionsumfang einer Application unkompliziert erweitert werden. Ein populäres Beispiel hierfür sind sicherlich d&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Mac OSX: starting postgres on boot by Carl</title>
		<link>http://www.luckydonkey.com/2008/07/03/mac-osx-starting-postgres-on-boot/comment-page-1/#comment-2581</link>
		<dc:creator>Carl</dc:creator>
		<pubDate>Mon, 29 Nov 2010 17:18:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.luckydonkey.com/?p=208#comment-2581</guid>
		<description>Heya! Thanks much for this. This seems to be one of the clearest explanations on Mac OS X PostgreSQL startup out there.

Would you mind if I link to this page from the PostgreSQL docs (9.0) on server startups?

Also: I too had the permissions error that Mike mentions. Even after his fix, sudo SystemStarter -n -D was reporting a failure to start (&quot;execution of Startup script failed&quot;). When I did restart anyway, however, postgres was running fine.</description>
		<content:encoded><![CDATA[<p>Heya! Thanks much for this. This seems to be one of the clearest explanations on Mac OS X PostgreSQL startup out there.</p>
<p>Would you mind if I link to this page from the PostgreSQL docs (9.0) on server startups?</p>
<p>Also: I too had the permissions error that Mike mentions. Even after his fix, sudo SystemStarter -n -D was reporting a failure to start (&#8220;execution of Startup script failed&#8221;). When I did restart anyway, however, postgres was running fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PostgreSQL, SQLAlchemy, Dropping all tables and sequences by mike bayer</title>
		<link>http://www.luckydonkey.com/2007/11/23/postgresql-sqlalchemy-dropping-all-tables-and-sequences/comment-page-1/#comment-2564</link>
		<dc:creator>mike bayer</dc:creator>
		<pubDate>Wed, 15 Sep 2010 13:54:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.luckydonkey.com/2007/11/23/postgresql-sqlalchemy-dropping-all-tables-and-sequences/#comment-2564</guid>
		<description>hiya -

Just saw this post tweeted so here&#039;s an update.  I have the ultimate &quot;drop everything&quot; script that now uses the Inspector to pull everything in - so far I&#039;ve tested with Postgresql and MS-SQL.    Though currently its doing just all the tables and related objects - I notice Pavel&#039;s script does views and routines too.   http://www.sqlalchemy.org/trac/wiki/UsageRecipes/DropEverything</description>
		<content:encoded><![CDATA[<p>hiya -</p>
<p>Just saw this post tweeted so here&#8217;s an update.  I have the ultimate &#8220;drop everything&#8221; script that now uses the Inspector to pull everything in &#8211; so far I&#8217;ve tested with Postgresql and MS-SQL.    Though currently its doing just all the tables and related objects &#8211; I notice Pavel&#8217;s script does views and routines too.   <a href="http://www.sqlalchemy.org/trac/wiki/UsageRecipes/DropEverything" rel="nofollow">http://www.sqlalchemy.org/trac/wiki/UsageRecipes/DropEverything</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on workingenv, easy_install, ez_setup&#8230; hmmm by pete morgan</title>
		<link>http://www.luckydonkey.com/2007/11/23/workingenv-easy_install-ez_setup-hmmm-2/comment-page-1/#comment-2556</link>
		<dc:creator>pete morgan</dc:creator>
		<pubDate>Fri, 30 Jul 2010 20:09:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.luckydonkey.com/2007/11/23/workingenv-easy_install-ez_setup-hmmm-2/#comment-2556</guid>
		<description>Bumped into this same problem, and your solution indicated a path problem.

I was inside a pylons project (a &quot;stuff/&quot; direcctory) with same result.

When I moved/executed the script in another directory ie ~ it worked fine.. 

strange.</description>
		<content:encoded><![CDATA[<p>Bumped into this same problem, and your solution indicated a path problem.</p>
<p>I was inside a pylons project (a &#8220;stuff/&#8221; direcctory) with same result.</p>
<p>When I moved/executed the script in another directory ie ~ it worked fine.. </p>
<p>strange.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PostgreSQL, SQLAlchemy, Dropping all tables and sequences by Pavel Sedek</title>
		<link>http://www.luckydonkey.com/2007/11/23/postgresql-sqlalchemy-dropping-all-tables-and-sequences/comment-page-1/#comment-2555</link>
		<dc:creator>Pavel Sedek</dc:creator>
		<pubDate>Thu, 22 Jul 2010 18:16:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.luckydonkey.com/2007/11/23/postgresql-sqlalchemy-dropping-all-tables-and-sequences/#comment-2555</guid>
		<description>Hello, here is an easy solution in plpgsql. You can then drop all views, sequences, tables and functions just with calling SELECT drop_db();

Method declaration:

CREATE OR REPLACE FUNCTION drop_db()
  RETURNS void AS
$BODY$
  DECLARE
    objname character varying;
  
  BEGIN

	FOR objname IN SELECT table_name FROM information_schema.views WHERE table_schema = &#039;public&#039; LOOP
		EXECUTE &#039;DROP VIEW &#039; &#124;&#124; objname ;
	END LOOP;
	
	FOR objname IN SELECT table_name FROM information_schema.tables WHERE table_schema = &#039;public&#039; LOOP
		EXECUTE &#039;DROP TABLE &#039; &#124;&#124; objname &#124;&#124; &#039; CASCADE &#039;;
	END LOOP;

	FOR objname IN SELECT sequence_name FROM information_schema.sequences WHERE sequence_schema = &#039;public&#039; LOOP
		EXECUTE &#039;DROP SEQUENCE &#039; &#124;&#124; objname &#124;&#124; &#039; CASCADE &#039;;
	END LOOP;

	FOR objname IN SELECT routine_name FROM information_schema.routines WHERE routine_schema = &#039;public&#039; LOOP
		CONTINUE WHEN objname = &#039;drop_db&#039;;
		EXECUTE &#039;DROP FUNCTION &#039; &#124;&#124; objname &#124;&#124; &#039;() &#039; ;
	END LOOP;
	
END;
$BODY$
  LANGUAGE &#039;plpgsql&#039; VOLATILE
  COST 100;</description>
		<content:encoded><![CDATA[<p>Hello, here is an easy solution in plpgsql. You can then drop all views, sequences, tables and functions just with calling SELECT drop_db();</p>
<p>Method declaration:</p>
<p>CREATE OR REPLACE FUNCTION drop_db()<br />
  RETURNS void AS<br />
$BODY$<br />
  DECLARE<br />
    objname character varying;</p>
<p>  BEGIN</p>
<p>	FOR objname IN SELECT table_name FROM information_schema.views WHERE table_schema = &#8216;public&#8217; LOOP<br />
		EXECUTE &#8216;DROP VIEW &#8216; || objname ;<br />
	END LOOP;</p>
<p>	FOR objname IN SELECT table_name FROM information_schema.tables WHERE table_schema = &#8216;public&#8217; LOOP<br />
		EXECUTE &#8216;DROP TABLE &#8216; || objname || &#8216; CASCADE &#8216;;<br />
	END LOOP;</p>
<p>	FOR objname IN SELECT sequence_name FROM information_schema.sequences WHERE sequence_schema = &#8216;public&#8217; LOOP<br />
		EXECUTE &#8216;DROP SEQUENCE &#8216; || objname || &#8216; CASCADE &#8216;;<br />
	END LOOP;</p>
<p>	FOR objname IN SELECT routine_name FROM information_schema.routines WHERE routine_schema = &#8216;public&#8217; LOOP<br />
		CONTINUE WHEN objname = &#8216;drop_db&#8217;;<br />
		EXECUTE &#8216;DROP FUNCTION &#8216; || objname || &#8216;() &#8216; ;<br />
	END LOOP;</p>
<p>END;<br />
$BODY$<br />
  LANGUAGE &#8216;plpgsql&#8217; VOLATILE<br />
  COST 100;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Mac OSX: starting postgres on boot by Saint</title>
		<link>http://www.luckydonkey.com/2008/07/03/mac-osx-starting-postgres-on-boot/comment-page-1/#comment-2546</link>
		<dc:creator>Saint</dc:creator>
		<pubDate>Mon, 03 May 2010 12:02:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.luckydonkey.com/?p=208#comment-2546</guid>
		<description>Worked like a charm! Thanks heaps!!</description>
		<content:encoded><![CDATA[<p>Worked like a charm! Thanks heaps!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Python Style Plugins Made Easy by Mark Johnson</title>
		<link>http://www.luckydonkey.com/2008/01/02/python-style-plugins-made-easy/comment-page-1/#comment-2537</link>
		<dc:creator>Mark Johnson</dc:creator>
		<pubDate>Sat, 06 Mar 2010 23:31:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.luckydonkey.com/2008/01/02/python-style-plugins-made-easy/#comment-2537</guid>
		<description>Cool Thanks for the article. I am just starting python and this will help a lot.</description>
		<content:encoded><![CDATA[<p>Cool Thanks for the article. I am just starting python and this will help a lot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SQLAlchemy-Migrate upgrade scripts in a transaction by dazza</title>
		<link>http://www.luckydonkey.com/2008/07/27/sqlalchemy-migrate-upgrade-scripts-in-a-transaction/comment-page-1/#comment-2536</link>
		<dc:creator>dazza</dc:creator>
		<pubDate>Tue, 16 Feb 2010 13:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.luckydonkey.com/?p=210#comment-2536</guid>
		<description>I should have updated this post, sorry I forgot, this doesn&#039;t work with new versions of SQLAlchemy. I&#039;m not sure why, I&#039;m not currently using SQLAlchemy.</description>
		<content:encoded><![CDATA[<p>I should have updated this post, sorry I forgot, this doesn&#8217;t work with new versions of SQLAlchemy. I&#8217;m not sure why, I&#8217;m not currently using SQLAlchemy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SQLAlchemy-Migrate upgrade scripts in a transaction by px</title>
		<link>http://www.luckydonkey.com/2008/07/27/sqlalchemy-migrate-upgrade-scripts-in-a-transaction/comment-page-1/#comment-2535</link>
		<dc:creator>px</dc:creator>
		<pubDate>Tue, 16 Feb 2010 12:37:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.luckydonkey.com/?p=210#comment-2535</guid>
		<description>Is it working? I see that SQLalchemy-migrate works with autocommit after each operation. But if upgrade fails dwongrade is called. Maybe there have to be some extra configuration of sqlalchemy-migrate that I don&#039;t know.</description>
		<content:encoded><![CDATA[<p>Is it working? I see that SQLalchemy-migrate works with autocommit after each operation. But if upgrade fails dwongrade is called. Maybe there have to be some extra configuration of sqlalchemy-migrate that I don&#8217;t know.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

