On 2013-03-13, Joe Van Dyk wrote:
> --047d7b6226a405604904d7d09001
> Content-Type: text/plain; charset=UTF-8
>
> On Wed, Mar 13, 2013 at 8:47 AM, Steve Crawford <
> scrawf...@pinpointresearch.com> wrote:
>
>> On 03/12/2013 09:05 PM, Perry Smith wrote:
>>
>>> To all who replied:
>>>
>>> Thank you.
On Wed, Mar 13, 2013 at 8:47 AM, Steve Crawford <
scrawf...@pinpointresearch.com> wrote:
> On 03/12/2013 09:05 PM, Perry Smith wrote:
>
>> To all who replied:
>>
>> Thank you. ...
>>
>>
>> I had not seriously considered pg_dump / pg_restore because I assumed it
>> would be fairly slow but I will e
On 03/12/2013 09:05 PM, Perry Smith wrote:
To all who replied:
Thank you. ...
I had not seriously considered pg_dump / pg_restore because I assumed
it would be fairly slow but I will experiment with pg_restore and
template techniques this weekend and see which ones prove viable.
Another pos
On Mar 12, 2013, at 8:09 PM, Joe Van Dyk wrote:
> On Mar 12, 2013, at 8:42 AM, Perry Smith wrote:
>
>>
>> The other thought is perhaps there is a "snap shot" type concept. I don't
>> see it in the list of SQL commands. A "snap shot" would do exactly what it
>> sounds like. It would take
To all who replied:
Thank you. I did typo. I meant "transaction" instead of truncate.
I had not seriously considered pg_dump / pg_restore because I assumed it would
be fairly slow but I will experiment with pg_restore and template techniques
this weekend and see which ones prove viable.
I kn
On Mar 12, 2013, at 8:42 AM, Perry Smith wrote:
I tried posting this from Google Groups but I did not see it come through
after an hour so this may be a duplicate message for some.
The current testing technique for things like Ruby On Rails has three
choices but all of the choices will not work
On Mar 12, 2013, at 8:41 AM, Perry Smith wrote:
>
>
> One choice would be to create the database, use it, and then drop it for each
> test. I would create the database from a template that already has data
> taken from the production database (and probably trimmed down to a small
> subset o
On 03/12/2013 08:41 AM, Perry Smith wrote:
One choice would be to create the database, use it, and then drop it for each
test. I would create the database from a template that already has data taken
from the production database (and probably trimmed down to a small subset of
it). This requi
