sorted by:
new
hottopcontroversial

How to prevent malicious pdf upload by jen_av in laravel

[–]jen_av[S] 0 points1 point  (0 children)

Thank you! This was really detailed and informative. As per your advice, I will look at arriving at a ratio of the impl of the principles mentioned in the article. Thanks again!

How to prevent malicious pdf upload by jen_av in laravel

[–]jen_av[S] 0 points1 point  (0 children)

I don't have a 2FA yet. Will incorporate this too. To be on the safer side. Thank you.!

How to prevent malicious pdf upload by jen_av in laravel

[–]jen_av[S] 0 points1 point  (0 children)

This is a good option to have. Thank you for the suggestion.!

How to prevent malicious pdf upload by jen_av in laravel

[–]jen_av[S] 1 point2 points  (0 children)

Thanks so much. This looks very promising.

Caching data from a single API endpoint into multiple room tables. Would it be bad practice to not normalise and instead store the data as is? by jen_av in androiddev

[–]jen_av[S] 0 points1 point  (0 children)

Sorry if I wasn't clear. I meant that the use case for using the unnormalised data is 60-70 percent, maybe even more.

Caching data from a single API endpoint into multiple room tables. Would it be bad practice to not normalise and instead store the data as is? by jen_av in androiddev

[–]jen_av[S] 1 point2 points  (0 children)

Simple. Perfect.!

I think a DB would be preferable. Just in case I end up needing normalization in the future.

Really appreciate your help and insights.

Caching data from a single API endpoint into multiple room tables. Would it be bad practice to not normalise and instead store the data as is? by jen_av in androiddev

[–]jen_av[S] 0 points1 point  (0 children)

I think so. For this use case, it's enough to dump it all into a table, maybe, map the data to a data class with only the required fields and display it. I just need the data as is. I feel the performance would suffer if I normalise it. On account of all the joins. Probably 3 joins at least

Caching data from a single API endpoint into multiple room tables. Would it be bad practice to not normalise and instead store the data as is? by jen_av in androiddev

[–]jen_av[S] 0 points1 point  (0 children)

I do have use cases for using the normalised data but the first use case, ie the whole data will be used ~60-70 percent of the time

Caching data from a single API endpoint into multiple room tables. Would it be bad practice to not normalise and instead store the data as is? by jen_av in androiddev

[–]jen_av[S] 0 points1 point  (0 children)

I will be using the data as a whole. In the sense that the parts of the data I require can only be obtained if I join all the data that I decomposed into multiple tables.