Google Material's ExpansionPanel for ReactJS not expanding by defaultSet a default parameter value for a JavaScript functionWhy does Google prepend while(1); to their JSON responses?ReactJS - Does render get called any time “setState” is called?ReactJs update parent after ComponentDidMount from child classGetting a child's default props to set the state in the parent in ReactJSReactJS ES2015 Child Components[React]: rendering through this.props.children always unmounts and mounts all children instead of just re-renderingag-grid - expanding/collapsing tree dataWhy is a change in my app state not causing a re-render in my child component?Why is child component not receiving updated value from parent in React Native?

Suggestions for protecting jeans from saddle clamp bolt

Correlation length anisotropy in the 2D Ising model

How did the SysRq key get onto modern keyboards if it's rarely used?

Pointwise convergence of uniformly continuous functions to zero, but not uniformly

Why does Canada require mandatory bilingualism in all government posts?

Trapped in an ocean Temple in Minecraft?

Did the meaning of "significant" change in the 20th century?

Am I allowed to use personal conversation as a source?

How do I explain an exponentially complex intuitively?

Defining a Function programmatically

What do I do with a party that is much stronger than their level?

Can anyone give a concrete example to illustrate what is an uniform prior?

Are there any examples of technologies have been lost over time?

Why can't my huge trees be chopped down?

Commercial jet accompanied by small plane near Seattle

Sci fi story: Clever pigs that help a galaxy lawman

How to avoid theft of potentially patentable IP when trying to obtain a Ph.D?

How could Nomadic scholars effectively memorize libraries worth of information

If my pay period is split between 2 calendar years, which tax year do I file them in?

What language is Raven using for her attack in the new 52?

Why force the nose of 737 Max down in the first place?

How much were the LMs maneuvered to their landing points?

Why didn't Britain or any other European power colonise Abyssinia/Ethiopia before 1936?

Why/when is AC-DC-AC conversion superior to direct AC-AC conversion?



Google Material's ExpansionPanel for ReactJS not expanding by default


Set a default parameter value for a JavaScript functionWhy does Google prepend while(1); to their JSON responses?ReactJS - Does render get called any time “setState” is called?ReactJs update parent after ComponentDidMount from child classGetting a child's default props to set the state in the parent in ReactJSReactJS ES2015 Child Components[React]: rendering through this.props.children always unmounts and mounts all children instead of just re-renderingag-grid - expanding/collapsing tree dataWhy is a change in my app state not causing a re-render in my child component?Why is child component not receiving updated value from parent in React Native?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








0















I am building a ReactJS app using Google's Material-UI.



I have the following child class that is displayed in a Grid, after a search has been submitted. Depending if the search is one type or another, the ExpansionPanel inside this child class should be expanded or not expanded.



Here is the class that is being mapped in the parent component:



The expandByDefault boolean is passed from the parent class.



class SearchResults extends React.Component 
render ()
const classes = this.props;
const batchAndContents = this.props;
const expandByDefault = this.props;
return (
<div>
<ExpansionPanel defaultExpanded=expandByDefault >
<ExpansionPanelSummary>
<Typography className=classes.heading>Box batchAndContents.sequenceCode</Typography>
</ExpansionPanelSummary>
<ExpansionPanelDetails>
<SearchResultsTable contents=batchAndContents.contents/>
</ExpansionPanelDetails>
</ExpansionPanel>
</div>
)




Here is the render method for the parent class:
You can see in SearchResults, my custom class, I pass a prop named expandByDefault.



render () 
return (
<div>
. . . . .
. . . . .
. . . . .
<Grid container spacing=24 style=padding: 24>
this.state.searchResults.map((searchResult) => (
<Grid item key=searchResult.sequenceCode+searchResult.state xs=12>
<SearchResults batchAndContents=searchResult expandByDefault=this.state.lastSearchType === "ContentBarcode"/>
</Grid>
))
</Grid>
</div>
)



I've tried several variations to get this to work, and I can't seem to understand what I'm missing.



What's interesting is that when I initially perform a search, and the ExpansionPanel's property defaultExpanded is set to true, it works. However if I don't refresh the page and perform another search with a different type, the results don't collapse back down when the type should cause that behavior.



Same behavior occurs if I initially perform the search and the ExpansionPanel defaultExpanded is set to false. It expands on click, and is default collapsed, however, when changing the search type to something that should cause default expanded panels, it doesn't work.



I appreciate any guidance.










share|improve this question






















  • You want expanded, not defaultExpanded.

    – Herohtar
    Mar 26 at 18:53











  • @Herohtar Thanks for your reply, that actually wasn't the issue, I posted my solution down below. Thank you!

    – Miguel J.
    Mar 26 at 19:19

















0















I am building a ReactJS app using Google's Material-UI.



I have the following child class that is displayed in a Grid, after a search has been submitted. Depending if the search is one type or another, the ExpansionPanel inside this child class should be expanded or not expanded.



Here is the class that is being mapped in the parent component:



The expandByDefault boolean is passed from the parent class.



class SearchResults extends React.Component 
render ()
const classes = this.props;
const batchAndContents = this.props;
const expandByDefault = this.props;
return (
<div>
<ExpansionPanel defaultExpanded=expandByDefault >
<ExpansionPanelSummary>
<Typography className=classes.heading>Box batchAndContents.sequenceCode</Typography>
</ExpansionPanelSummary>
<ExpansionPanelDetails>
<SearchResultsTable contents=batchAndContents.contents/>
</ExpansionPanelDetails>
</ExpansionPanel>
</div>
)




Here is the render method for the parent class:
You can see in SearchResults, my custom class, I pass a prop named expandByDefault.



render () 
return (
<div>
. . . . .
. . . . .
. . . . .
<Grid container spacing=24 style=padding: 24>
this.state.searchResults.map((searchResult) => (
<Grid item key=searchResult.sequenceCode+searchResult.state xs=12>
<SearchResults batchAndContents=searchResult expandByDefault=this.state.lastSearchType === "ContentBarcode"/>
</Grid>
))
</Grid>
</div>
)



I've tried several variations to get this to work, and I can't seem to understand what I'm missing.



What's interesting is that when I initially perform a search, and the ExpansionPanel's property defaultExpanded is set to true, it works. However if I don't refresh the page and perform another search with a different type, the results don't collapse back down when the type should cause that behavior.



Same behavior occurs if I initially perform the search and the ExpansionPanel defaultExpanded is set to false. It expands on click, and is default collapsed, however, when changing the search type to something that should cause default expanded panels, it doesn't work.



I appreciate any guidance.










share|improve this question






















  • You want expanded, not defaultExpanded.

    – Herohtar
    Mar 26 at 18:53











  • @Herohtar Thanks for your reply, that actually wasn't the issue, I posted my solution down below. Thank you!

    – Miguel J.
    Mar 26 at 19:19













0












0








0








I am building a ReactJS app using Google's Material-UI.



I have the following child class that is displayed in a Grid, after a search has been submitted. Depending if the search is one type or another, the ExpansionPanel inside this child class should be expanded or not expanded.



Here is the class that is being mapped in the parent component:



The expandByDefault boolean is passed from the parent class.



class SearchResults extends React.Component 
render ()
const classes = this.props;
const batchAndContents = this.props;
const expandByDefault = this.props;
return (
<div>
<ExpansionPanel defaultExpanded=expandByDefault >
<ExpansionPanelSummary>
<Typography className=classes.heading>Box batchAndContents.sequenceCode</Typography>
</ExpansionPanelSummary>
<ExpansionPanelDetails>
<SearchResultsTable contents=batchAndContents.contents/>
</ExpansionPanelDetails>
</ExpansionPanel>
</div>
)




Here is the render method for the parent class:
You can see in SearchResults, my custom class, I pass a prop named expandByDefault.



render () 
return (
<div>
. . . . .
. . . . .
. . . . .
<Grid container spacing=24 style=padding: 24>
this.state.searchResults.map((searchResult) => (
<Grid item key=searchResult.sequenceCode+searchResult.state xs=12>
<SearchResults batchAndContents=searchResult expandByDefault=this.state.lastSearchType === "ContentBarcode"/>
</Grid>
))
</Grid>
</div>
)



I've tried several variations to get this to work, and I can't seem to understand what I'm missing.



What's interesting is that when I initially perform a search, and the ExpansionPanel's property defaultExpanded is set to true, it works. However if I don't refresh the page and perform another search with a different type, the results don't collapse back down when the type should cause that behavior.



Same behavior occurs if I initially perform the search and the ExpansionPanel defaultExpanded is set to false. It expands on click, and is default collapsed, however, when changing the search type to something that should cause default expanded panels, it doesn't work.



I appreciate any guidance.










share|improve this question














I am building a ReactJS app using Google's Material-UI.



I have the following child class that is displayed in a Grid, after a search has been submitted. Depending if the search is one type or another, the ExpansionPanel inside this child class should be expanded or not expanded.



Here is the class that is being mapped in the parent component:



The expandByDefault boolean is passed from the parent class.



class SearchResults extends React.Component 
render ()
const classes = this.props;
const batchAndContents = this.props;
const expandByDefault = this.props;
return (
<div>
<ExpansionPanel defaultExpanded=expandByDefault >
<ExpansionPanelSummary>
<Typography className=classes.heading>Box batchAndContents.sequenceCode</Typography>
</ExpansionPanelSummary>
<ExpansionPanelDetails>
<SearchResultsTable contents=batchAndContents.contents/>
</ExpansionPanelDetails>
</ExpansionPanel>
</div>
)




Here is the render method for the parent class:
You can see in SearchResults, my custom class, I pass a prop named expandByDefault.



render () 
return (
<div>
. . . . .
. . . . .
. . . . .
<Grid container spacing=24 style=padding: 24>
this.state.searchResults.map((searchResult) => (
<Grid item key=searchResult.sequenceCode+searchResult.state xs=12>
<SearchResults batchAndContents=searchResult expandByDefault=this.state.lastSearchType === "ContentBarcode"/>
</Grid>
))
</Grid>
</div>
)



I've tried several variations to get this to work, and I can't seem to understand what I'm missing.



What's interesting is that when I initially perform a search, and the ExpansionPanel's property defaultExpanded is set to true, it works. However if I don't refresh the page and perform another search with a different type, the results don't collapse back down when the type should cause that behavior.



Same behavior occurs if I initially perform the search and the ExpansionPanel defaultExpanded is set to false. It expands on click, and is default collapsed, however, when changing the search type to something that should cause default expanded panels, it doesn't work.



I appreciate any guidance.







javascript reactjs material-ui






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 26 at 18:44









Miguel J.Miguel J.

14213 bronze badges




14213 bronze badges












  • You want expanded, not defaultExpanded.

    – Herohtar
    Mar 26 at 18:53











  • @Herohtar Thanks for your reply, that actually wasn't the issue, I posted my solution down below. Thank you!

    – Miguel J.
    Mar 26 at 19:19

















  • You want expanded, not defaultExpanded.

    – Herohtar
    Mar 26 at 18:53











  • @Herohtar Thanks for your reply, that actually wasn't the issue, I posted my solution down below. Thank you!

    – Miguel J.
    Mar 26 at 19:19
















You want expanded, not defaultExpanded.

– Herohtar
Mar 26 at 18:53





You want expanded, not defaultExpanded.

– Herohtar
Mar 26 at 18:53













@Herohtar Thanks for your reply, that actually wasn't the issue, I posted my solution down below. Thank you!

– Miguel J.
Mar 26 at 19:19





@Herohtar Thanks for your reply, that actually wasn't the issue, I posted my solution down below. Thank you!

– Miguel J.
Mar 26 at 19:19












2 Answers
2






active

oldest

votes


















-1














The defaultExpanded property only defines the default state of the component -- ie, whether or not to expand the panel when it is first rendered. Changes to this value later will not affect whether the panel is currently expanded or not.



To cause the panel to expand or collapse in response to changes in your app, you need to use the expanded property. From the docs:




If true, expands the panel, otherwise collapse it. Setting this prop enables control over the panel.







share|improve this answer























  • Hey, thank you for your response! The component itself actually toggle open and closed without having to manually manage it. I understand that you can set an onClick action listener, then toggle it open or closed. I actually found out the problem, I'll post in a second. Thanks again.

    – Miguel J.
    Mar 26 at 19:07


















-1














The problem here is that the keys that are on the <Grid item ... /> elements in the <Grid container /> parent view are not changing.



When a search is executed with a different type, the same data is being displayed, just displayed differently.



From my understanding, if react sees the same key with the same data, it doesn't need to re-render, even if there are states being passed as props to the children. In my case states are being passed as props to children in a <Grid item ... />.



As a resolution, I append the type of search to the key. So now when the search type changes, the key that holds the result does as well, and the children of the <Grid item ... /> are triggered to be re-rendered.



Sorry for not the best explanation, I have some practical experience with ReactJS, but I can not speak about it that well from an "under the hood" point of view.






share|improve this answer























  • That's basically what my answer was getting at; you can't use defaultExpanded since the components aren't being re-rendered. However, forcing React to re-render the components isn't an ideal solution as it will reduce performance and impact the users' experience. expanded would be the better option and a bit simpler, unless you also need to allow those panels to be expanded/collapsed by the user, in which case you would need to add some additional logic.

    – Herohtar
    Mar 26 at 19:53














Your Answer






StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55364249%2fgoogle-materials-expansionpanel-for-reactjs-not-expanding-by-default%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









-1














The defaultExpanded property only defines the default state of the component -- ie, whether or not to expand the panel when it is first rendered. Changes to this value later will not affect whether the panel is currently expanded or not.



To cause the panel to expand or collapse in response to changes in your app, you need to use the expanded property. From the docs:




If true, expands the panel, otherwise collapse it. Setting this prop enables control over the panel.







share|improve this answer























  • Hey, thank you for your response! The component itself actually toggle open and closed without having to manually manage it. I understand that you can set an onClick action listener, then toggle it open or closed. I actually found out the problem, I'll post in a second. Thanks again.

    – Miguel J.
    Mar 26 at 19:07















-1














The defaultExpanded property only defines the default state of the component -- ie, whether or not to expand the panel when it is first rendered. Changes to this value later will not affect whether the panel is currently expanded or not.



To cause the panel to expand or collapse in response to changes in your app, you need to use the expanded property. From the docs:




If true, expands the panel, otherwise collapse it. Setting this prop enables control over the panel.







share|improve this answer























  • Hey, thank you for your response! The component itself actually toggle open and closed without having to manually manage it. I understand that you can set an onClick action listener, then toggle it open or closed. I actually found out the problem, I'll post in a second. Thanks again.

    – Miguel J.
    Mar 26 at 19:07













-1












-1








-1







The defaultExpanded property only defines the default state of the component -- ie, whether or not to expand the panel when it is first rendered. Changes to this value later will not affect whether the panel is currently expanded or not.



To cause the panel to expand or collapse in response to changes in your app, you need to use the expanded property. From the docs:




If true, expands the panel, otherwise collapse it. Setting this prop enables control over the panel.







share|improve this answer













The defaultExpanded property only defines the default state of the component -- ie, whether or not to expand the panel when it is first rendered. Changes to this value later will not affect whether the panel is currently expanded or not.



To cause the panel to expand or collapse in response to changes in your app, you need to use the expanded property. From the docs:




If true, expands the panel, otherwise collapse it. Setting this prop enables control over the panel.








share|improve this answer












share|improve this answer



share|improve this answer










answered Mar 26 at 19:01









HerohtarHerohtar

3,3892 gold badges20 silver badges29 bronze badges




3,3892 gold badges20 silver badges29 bronze badges












  • Hey, thank you for your response! The component itself actually toggle open and closed without having to manually manage it. I understand that you can set an onClick action listener, then toggle it open or closed. I actually found out the problem, I'll post in a second. Thanks again.

    – Miguel J.
    Mar 26 at 19:07

















  • Hey, thank you for your response! The component itself actually toggle open and closed without having to manually manage it. I understand that you can set an onClick action listener, then toggle it open or closed. I actually found out the problem, I'll post in a second. Thanks again.

    – Miguel J.
    Mar 26 at 19:07
















Hey, thank you for your response! The component itself actually toggle open and closed without having to manually manage it. I understand that you can set an onClick action listener, then toggle it open or closed. I actually found out the problem, I'll post in a second. Thanks again.

– Miguel J.
Mar 26 at 19:07





Hey, thank you for your response! The component itself actually toggle open and closed without having to manually manage it. I understand that you can set an onClick action listener, then toggle it open or closed. I actually found out the problem, I'll post in a second. Thanks again.

– Miguel J.
Mar 26 at 19:07













-1














The problem here is that the keys that are on the <Grid item ... /> elements in the <Grid container /> parent view are not changing.



When a search is executed with a different type, the same data is being displayed, just displayed differently.



From my understanding, if react sees the same key with the same data, it doesn't need to re-render, even if there are states being passed as props to the children. In my case states are being passed as props to children in a <Grid item ... />.



As a resolution, I append the type of search to the key. So now when the search type changes, the key that holds the result does as well, and the children of the <Grid item ... /> are triggered to be re-rendered.



Sorry for not the best explanation, I have some practical experience with ReactJS, but I can not speak about it that well from an "under the hood" point of view.






share|improve this answer























  • That's basically what my answer was getting at; you can't use defaultExpanded since the components aren't being re-rendered. However, forcing React to re-render the components isn't an ideal solution as it will reduce performance and impact the users' experience. expanded would be the better option and a bit simpler, unless you also need to allow those panels to be expanded/collapsed by the user, in which case you would need to add some additional logic.

    – Herohtar
    Mar 26 at 19:53
















-1














The problem here is that the keys that are on the <Grid item ... /> elements in the <Grid container /> parent view are not changing.



When a search is executed with a different type, the same data is being displayed, just displayed differently.



From my understanding, if react sees the same key with the same data, it doesn't need to re-render, even if there are states being passed as props to the children. In my case states are being passed as props to children in a <Grid item ... />.



As a resolution, I append the type of search to the key. So now when the search type changes, the key that holds the result does as well, and the children of the <Grid item ... /> are triggered to be re-rendered.



Sorry for not the best explanation, I have some practical experience with ReactJS, but I can not speak about it that well from an "under the hood" point of view.






share|improve this answer























  • That's basically what my answer was getting at; you can't use defaultExpanded since the components aren't being re-rendered. However, forcing React to re-render the components isn't an ideal solution as it will reduce performance and impact the users' experience. expanded would be the better option and a bit simpler, unless you also need to allow those panels to be expanded/collapsed by the user, in which case you would need to add some additional logic.

    – Herohtar
    Mar 26 at 19:53














-1












-1








-1







The problem here is that the keys that are on the <Grid item ... /> elements in the <Grid container /> parent view are not changing.



When a search is executed with a different type, the same data is being displayed, just displayed differently.



From my understanding, if react sees the same key with the same data, it doesn't need to re-render, even if there are states being passed as props to the children. In my case states are being passed as props to children in a <Grid item ... />.



As a resolution, I append the type of search to the key. So now when the search type changes, the key that holds the result does as well, and the children of the <Grid item ... /> are triggered to be re-rendered.



Sorry for not the best explanation, I have some practical experience with ReactJS, but I can not speak about it that well from an "under the hood" point of view.






share|improve this answer













The problem here is that the keys that are on the <Grid item ... /> elements in the <Grid container /> parent view are not changing.



When a search is executed with a different type, the same data is being displayed, just displayed differently.



From my understanding, if react sees the same key with the same data, it doesn't need to re-render, even if there are states being passed as props to the children. In my case states are being passed as props to children in a <Grid item ... />.



As a resolution, I append the type of search to the key. So now when the search type changes, the key that holds the result does as well, and the children of the <Grid item ... /> are triggered to be re-rendered.



Sorry for not the best explanation, I have some practical experience with ReactJS, but I can not speak about it that well from an "under the hood" point of view.







share|improve this answer












share|improve this answer



share|improve this answer










answered Mar 26 at 19:18









Miguel J.Miguel J.

14213 bronze badges




14213 bronze badges












  • That's basically what my answer was getting at; you can't use defaultExpanded since the components aren't being re-rendered. However, forcing React to re-render the components isn't an ideal solution as it will reduce performance and impact the users' experience. expanded would be the better option and a bit simpler, unless you also need to allow those panels to be expanded/collapsed by the user, in which case you would need to add some additional logic.

    – Herohtar
    Mar 26 at 19:53


















  • That's basically what my answer was getting at; you can't use defaultExpanded since the components aren't being re-rendered. However, forcing React to re-render the components isn't an ideal solution as it will reduce performance and impact the users' experience. expanded would be the better option and a bit simpler, unless you also need to allow those panels to be expanded/collapsed by the user, in which case you would need to add some additional logic.

    – Herohtar
    Mar 26 at 19:53

















That's basically what my answer was getting at; you can't use defaultExpanded since the components aren't being re-rendered. However, forcing React to re-render the components isn't an ideal solution as it will reduce performance and impact the users' experience. expanded would be the better option and a bit simpler, unless you also need to allow those panels to be expanded/collapsed by the user, in which case you would need to add some additional logic.

– Herohtar
Mar 26 at 19:53






That's basically what my answer was getting at; you can't use defaultExpanded since the components aren't being re-rendered. However, forcing React to re-render the components isn't an ideal solution as it will reduce performance and impact the users' experience. expanded would be the better option and a bit simpler, unless you also need to allow those panels to be expanded/collapsed by the user, in which case you would need to add some additional logic.

– Herohtar
Mar 26 at 19:53


















draft saved

draft discarded
















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55364249%2fgoogle-materials-expansionpanel-for-reactjs-not-expanding-by-default%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Kamusi Yaliyomo Aina za kamusi | Muundo wa kamusi | Faida za kamusi | Dhima ya picha katika kamusi | Marejeo | Tazama pia | Viungo vya nje | UrambazajiKuhusu kamusiGo-SwahiliWiki-KamusiKamusi ya Kiswahili na Kiingerezakuihariri na kuongeza habari

SQL error code 1064 with creating Laravel foreign keysForeign key constraints: When to use ON UPDATE and ON DELETEDropping column with foreign key Laravel error: General error: 1025 Error on renameLaravel SQL Can't create tableLaravel Migration foreign key errorLaravel php artisan migrate:refresh giving a syntax errorSQLSTATE[42S01]: Base table or view already exists or Base table or view already exists: 1050 Tableerror in migrating laravel file to xampp serverSyntax error or access violation: 1064:syntax to use near 'unsigned not null, modelName varchar(191) not null, title varchar(191) not nLaravel cannot create new table field in mysqlLaravel 5.7:Last migration creates table but is not registered in the migration table

은진 송씨 목차 역사 본관 분파 인물 조선 왕실과의 인척 관계 집성촌 항렬자 인구 같이 보기 각주 둘러보기 메뉴은진 송씨세종실록 149권, 지리지 충청도 공주목 은진현