|Product Name||The Fall Of The House Of Dixie: The Civil War And The Social Revolution That Transformed The South|
|Category||Book / Magazine / Publication|
|Amazon.com||Buy on Amazon ~ 1400067030|
|Price New||15.65 US Dollars (curriencies)|
|Price Used||4.77 US Dollars (curriencies)|
|Width||1.36 inches (convert)|
|Height||9.5 inches (convert)|
|Length||6.34 inches (convert)|
|Weight||27.84 ounces (convert)|
|Long Description||In this major new history of the Civil War, Bruce Levine tells the riveting story of how that conflict upended the economic, political, and social life of the old South, utterly destroying the Confederacy and the society it represented and defended. Told through the words of the people who lived it, The Fall of the House of Dixie illuminates the way a war undertaken to preserve the status quo became a second American Revolution whose impact on the country was as strong and lasting as that of our first. In 1860 the American South was a vast, wealthy, imposing region where a small minority had amassed great political power and enormous fortunes through a system of forced labor. The South’s large population of slaveless whites almost universally supported the basic interests of plantation owners, despite the huge wealth gap that separated them. By the end of 1865 these structures of wealth and power had been shattered. Millions of black people had gained their freedom, many poorer whites had ceased following their wealthy neighbors, and plantation owners were brought to their knees, losing not only their slaves but their political power, their worldview, their very way of life. This sea change was felt nationwide, as the balance of power in Congress, the judiciary, and the presidency shifted dramatically and lastingly toward the North, and the country embarked on a course toward equal rights. Levinecaptures the many-sided human drama of this story using a huge trove of diaries, letters, newspaper articles, government documents, and more. In The Fall of the House of Dixie, the true stakes of the Civil War become clearer than ever before, as slaves battle for their freedom in the face of brutal reprisals; Abraham Lincoln and his party turn what began as a limited war for the Union into a crusade against slavery by issuing the Emancipation Proclamation; poor southern whites grow increasingly disillusioned with fighting what they have come to see as the plantation owners’ war; and the slave owners grow ever more desperate as their beloved social order is destroyed, not just by the Union Army, but also from within. When the smoke clears, not only Dixie but all of American society is changed forever. Brilliantly argued and engrossing, The Fall of the House of Dixie is a sweeping account of the destruction of the old South during the Civil War, offering a fresh perspective on the most colossal struggle in our history and the new world it brought into being. Praise for The Fall of the House of Dixie “This is the Civil War as it is seldom seen. . . . A portrait of a country in transition . . . as vivid as any that has been written.” — The Boston Globe “An absorbing social history . . . For readers whose Civil War bibliography runs to standard works by Bruce Catton and James McPherson, [Bruce] Levine’s book offers fresh insights.” — The Wall Street Journal “More poignantly than any book before, The Fall of the House of Dixie shows how deeply intertwined the Confederacy was with slavery, and how the destruction of both made possible a ‘second American revolution’ as far-reaching as the first.” —David W. Blight, author of American Oracle “Splendidly colorful . . . Levine recounts this tale of Southern institutional rot with the ease and authority born of decades of study.” — Kirkus Reviews (starred review) “A deep, rich, and complex analysis of the period surrounding and including the American Civil War.” — Publishers Weekly (starred review)|
|Similar Items||9780143113904: Reading The Man: A Portrait Of Robert E. Lee Through His Private Letters|
9780140216981: Half Slave And Half Free, Revised Edition: The Roots Of Civil War
9780099280903: Gettysburg: The Last Invasion
9780061319297: The Impending Crisis, 1848-1861
9780060964313: Reconstruction: America's Unfinished Revolution, 1863-1877
9780060937164: Reconstruction: America's Unfinished Revolution, 1863-1877
9780060842383: Snow-Storm In August: Washington City, Francis Scott Key, And The Forgotten Race Riot Of 1835
9780060807597: River Of Dark Dreams: Slavery And Empire In The Cotton Kingdom
9780060158514: Reconstruction: America's Unfinished Revolution, 1863-1877 (New American Nation Series)
9780029099131: American Oracle: The Civil War In The Civil Rights Era
View 59 more similar items
|Search Google||by EAN or by Title|
Article of interest
This feature started with version 3.3 of the API and it allows you to update many fields of a product in one call. Prior to this, each attribute for a product was updated in a separate call, causing the process to be a bit slow.
It is important to note that bulk updates only work with JSON formatted data. Because of this, you can leave the mode=json out of your call.
You should use a POST call instead of a GET to avoid over running the length limits that can be found when sending long URLs.
- keycode - your normal API keycode
- update - the first product you intend to update (more info below)
- field - must be set to *bulk*
- test - If you are using GET (please don't) this should be the first parm. Set it to test=1 to avoid saving any actual data.
- imageURL - This is case sensitive. This can be any reachable image in jpg, gif, png format. You can use ftp, http, https and even data URLs here. So rather than pushing in a separate call, we will pull it.
- fields - This is the JSON formatted array of fields to be updated. Yes, this is actually optional. But without it, we won't update any field data.
- errorsonly=1 - If you add this to the request, any fields that update without error not be returned. If multiple products are updated, any product with no errors in any field will be completely omitted.
- dupesok=1 - If you add this to your request, fields that try to update with duplicate values will be considered good and will return "ok" instead of the normal "duplicate" return value.
- returnval=1 - If you add this to your request, the value is returned along with the status for each field you update. Normally the value is omitted to save on data packet size. May be useful when debugging.
Each entry in the fields array is made up of keys and data. Some keys are required and some are optional depending on the data type being used. These entries mirror the single field update calls used when updating data one field at a time.
Details of the fields entries
- field - required, the name of the field to be updated
- value - required, the new value for this field
- extra_id - optional, Some fields use 2 fields to store the data. One being a numeric value and the second being a descriptor [such as a ounces, gallons, quarts] This extra value must match the list we keep in our database. You can include the text version of this extra information at the end of the "value" field but it still needs to match what we have. You can also split the value into two fields the way we do passing the number in the "value" field and the descriptor as an index id in this "extra_id" field. For more information, see the "get=extra" in the basic overview for the v3 API.
- reason - used only when you want to delete a field. If you use this, you must set the value field to empty string and give a reason in this field. At least 13 characters are required for this reason.
An example of the JSON to update multiple fields for a single product
The order of each field in the array doesn't matter. We will process them in sequence but sequence makes no difference. So you don't have to sort them or place them in any partcular order.
You can actually update multiple products at the same time. To do this, you still need to pass some basic information for the first product in the required fields (see above). But in the fields JSON, you create an array of products, each with a fields sub-array. The product listed in the update field would be ignored for the most part but must still be valid. So it can be hardcoded when using this method as long as it is a vaild EAN code.
An example of the JSON to update multiple fields for multiple products
It doesn't matter if you are updating a single product or multiple products. When the response is returned, the top level status is always going to be code 200 assuming your required fields passed the test. Then you will see an array of products even if you only passed in one to be updated. Each product entry and each field entry will have a status so you will know if individual updates worked or failed. This includes the imageURL you passed.
An example of the JSON returned after an update call
The return results in each img or status field
- ok - The field or image processed without error
- n/a - No image was sent (not for fields)
- duplicate - The data you sent already exists. (not for images)
- Any other value is an error which may include details but may not.
Examples of how to update images
Here are two examples of updating images. These both use a GET that you can test in your browser as soon as you insert your keycode. No other fields are being updated in these two examples. You would normally want to use POST in your code because there can be issues with very long GET requests losing data off the end. But these examples will work properly as GET or POST.
This first example is updating a single product image in simple mode using only form variables (no JSON)
This next example is also updating a single product image, but because it is using JSON, you could pass multiple products in the outer "fields" array. Notice that each inner product block also has a "fields" list when using JSON.