Danava dynasty
The Danava dynasty was the first legendary line of rulers in Pragjyotisha, established by Mahiranga Danava.[4] The dynasty was of Kachari origin. Mahiranga was sanskritized from Mairong. These rulers are mentioned in the Kalika Purana though there are no archaeological evidence.
Pragjyotisha Kingdom | |||||||
---|---|---|---|---|---|---|---|
Status | Mythological | ||||||
Government | Monarchical | ||||||
Historical era | Iron age | ||||||
|
Part of a series on the |
History of Assam |
---|
Proto-historic |
Late Medieval |
Modern |
Contemporary |
Categories |
|
Part of a series on the |
Culture of Assam |
---|
Proto-historic
Classical Medieval
Modern |
|
Festivals
|
Religion Major
Others |
History
Archives
Genres
Institutions
Awards
|
Music and performing arts |
Media |
Symbols
|
The Danava dynasty consisted of Kirata chiefs; the last of whom, Ghatakasura, was killed and replaced by Naraka.[5]
Chronology
- Mahiranga (Sankritised form of Mairang, 'Mai' means paddy and 'rang' means to remove the husks in Kachari language)
- Hatakasura
- Sambarasura
- Ratnasura
- Ghatakasura
Notes
- "639 Identifier Documentation: aho – ISO 639-3". SIL International (formerly known as the Summer Institute of Linguistics). SIL International. Retrieved 29 June 2019.
Ahom [aho]
- "Population by Religious Communities". Census India – 2001. Ministry of Home Affairs, Government of India. Retrieved 1 July 2019.
Census Data Finder/C Series/Population by Religious Communities
- "Population by religion community – 2011". Census of India, 2011. The Registrar General & Census Commissioner, India. Archived from the original on 25 August 2015.
- (Gait 1906, p. 11)
- (Gait 1906, p. 12)
gollark: This part of the program is particularly great.
gollark: Well, my code is generally kind of unpleasant, but this particular bit is fine.
gollark: This is "Rust" "code". It has a perfectly reasonable amount of symbols.
gollark: It also doesn't have generics, so I can't make a smart pointer which works for any type without `void*`, which is type-unsafe.
gollark: If I make my own smart pointers, then I'm pretty sure I have to manually sprinkle my code with macrons/function calls to do things to them, because the macros are bad token substitution things and not powerful enough to add them appropriately.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.