I'm sure you already discovered that you can right click on any object and only backup, create the sql for the object. Just that you might have missed it.
Johnf On Tuesday 08 September 2009 12:04:18 pm Jeff Johnson wrote: > pgAdminIII was working fine. It was creating the public schema as well > as my schema so when I executed it I get numerous errors because public > already existed. I removed all of the public schema commands and I have > a script where I could create duplicate schemas at will. To work with a > schema you can do a SET search_path = schema or qualify the table with > schema.table. Pretty slick once you get the hang of it. > > Thanks everyone for your help. > > John wrote: > > On Saturday 05 September 2009 07:54:04 am Jeff Johnson wrote: > >> Ed: Thanks for looking this up. I have been fighting with pg_dump all > >> day. It is not perfect. It creates several lines that are not > >> understood when creating the new schema (syntax errors) and I don't know > >> enough yet to fix all of them. > >> > >> But I will keep flogging away at it. > > > > I use pgAdmin3 for such duties. But there are many such admin type > > programs available. After you create the first database you can use the > > tools to create others by copying sql commands. > > > > > > On a side note please let us know how well the dbPostgres.py does with > > multi-schemas. When I was testing it worked well but I have not used > > mult-schemas in my personal projects since my early testing. > > > > > > Johnf _______________________________________________ Post Messages to: Dabo-users@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/200909081206.09236.jfabi...@yolo.com
