|
Please be very sure this is a real use case, it is often identified as a problem by management or an inexperienced developer as something that can/might happen but they have no real idea if the application requires this level of engineering.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Sure. thanks. I'll try to share a pic of what I originally thought.
|
|
|
|
|
IMO, we start with an empty database and then keep on adding the tables/procedures as needed by that sprint. We do not design entire database upfront. Assuming this to be true, will code first approach (except for data loss) would be quicker for developers? Or database first approach will also be fine depending on comfort level of person working?
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
Both should be fine providing you establish a good model for publishing migrations in advance. Don't find yourself requiring migrations without a pre-set strategy; that's long nights and extra downtime just waiting to happen.
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
|
|
|
|
|
I am assuming by migration you are referring to database increments. I guess the sprints have to be planned in a way that DB changes are incremental instead of breaking changes as much as possible.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
For a Database-First approach, yes. For Code-First there is a system built into EF called Migrations which will attempt to update the database to match the new code models without corrupting it:
Code First Migrations - EF6 | Microsoft Docs
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
|
|
|
|
|
Ah OK. Never used code first approach so wasn't aware of this. I feel at home when I can write my own scripts. However, I am not the one writing them this time so will leave it for others to decide. Thanks for help.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
Caveat - I have never used EF.
Code first always seems like a recipe for disaster to me and the thought of multiple developers managing your data structure just curls my toes in horror. Having seen what some senior developers can do to a normalised database I'd hate to see what a junior dev could do.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Mycroft Holmes wrote: Code first always seems like a recipe for disaster to me
I have used EF but never code first way. I don't like when the power is taken away from me. SQL scripts are powerful addiction you see.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
The day I think EF can write a better query or create a data structure better than I can I will quit, oh wait I have retired
Old dogs and all that, I cut my teeth on TSQL and will never abdicate that job although I am uncomfortable with CTEs.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Mycroft Holmes wrote: your data structure just curls my toes in horror
Unless you get paid based on billable hours. Then it is gleeful laughter all the way to the bank.
|
|
|
|
|
lw@zi wrote: IMO, we start with an empty database and then keep on adding the tables/procedures as needed by that sprint
That is the claim.
Think about do you want to live in a house where first they built the door, then the living room, then the kitchen, but first they needed to move the door because the kitchen made that door impossible...
Not to mention of course in the above I mentioned nothing about electricity nor plumbing.
|
|
|
|
|
That is where a very well thought sprint plan comes in. One must spend a really good amount of time modularizing (yes, that is a word from now on) the application, understanding dependencies and then planning the sprint so we do not end up in situations like:
Oh I can't add this new not null column to table anymore unless I set a default value. But there is no default value. Plus I can simply recreate this single table because 20 other tables and my in-laws don't approve of it.
Still, there is a good chance of getting into troubles. Fortunately this is not for me to decide (sprint planning, that is).
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
lw@zi wrote: That is where a very well thought sprint plan comes in
Yes the process that goes on before one starts sprints at all. And at a minimum there should be quite a few data model entities and primary attributes defined by that.
And real sizing also. Better know if you are going to have 10 users or 20 million users, and 10 TPS or 1 million TPS before you start your first 2 week sprint with an empty database.
|
|
|
|
|
Why don't you just have a "sprint", where y'all get together, and "design the database"?
Agile doesn't mean haphazard.
The idea that you can then "share" the model (while maintaining control) seems to be lost.
"Code first" means the "entities" are (initialy) "defined" via "code"; instead of "DDL first"; the result is still "SQL".
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
lw@zi wrote: IMO, we start with an empty database and then keep on adding the tables/procedures as needed by that sprint. We do not design entire database upfront. Most people think that, even if they don't "agile". That's the reason why many relational databases aren't normalized and contain inconsistencies.
It is a bad excuse for being lazy
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
<pre>$sql = "SELECT `name`, `email`, `comment` FROM `blog1`";
$result = $conn->query( $sql );
$count = 0;
$images = array("user1.jpg", "user2.jpg", "user3.jpg");
if( $result->num_rows > 0 ) {
while( $row = $result->fetch_assoc() ) {
echo '
<div class="comment-block">
'.( !empty( $images[$count] ) ? '<img src="images/blog/'.$images[$count].'">' : '').' <!-- Add the count to the images to use it as a key, add check to see if count is a key -->
'.$row['name'].'
'.$row['comment'].'
</div>
';
$count++; you want
if( $count == 3 )
{
$count = 0;
}
}
}
<pre><pre lang="PHP">
.
I tried to figure by my self but it wont work,like put images in div echo '
|
|
|
|
|
This forum is intended for questions about application architecture and design, not questions about web development. You should post your question in the web development forum.
This space for rent
|
|
|
|
|
can anybody move question in right place i am not familliar how to do it.
helpppp me
modified 16-Aug-18 15:06pm.
|
|
|
|
|
Post in this[^] forum.
This space for rent
|
|
|
|
|
What language is "helpppp" and what does it mean?
Sorry to be pedantic, but you will get more people not just willing, but able to help, if you stick to standard English ... txt spk makes you look childish, but seriously there are members here whose first language is not English, they are going to struggle to understand the "ppp" or the "plzzzz" etc. Keep your questions open to the widest possible audience. Help us to help you 
|
|
|
|
|
I have used several "how to" tutorials / instructions and still cannot figure out "who is on first" when it comes to activating wireless connection - IN GENERAL
I can do " ifconfig" , "wpa_supplicant.conf " etc.
I did use wicd and could not make the connection.
What I am missing is - <b>how does Linux starts / makes wireless connection in general.</b> . In what sequence and which files are involved.
PS I have SSH working and it was much easier to install / activate/ test.
Any pointers would be appreciated.
Please no references to RPi tutorial(s) needed, been there, done that,
Thanks
Vaclav
|
|
|
|
|
Wireless is the same as wired, it is just a network connection. The decision of 'who is on first' is decided by the systems that are connected to the network. Servers listen, and clients call. But servers can also be clients, and clients can be servers. Just the same as the telephone.
|
|
|
|
|
There's a couple of different ways to do this:
If you want to optimize you will need to manually configure the connection in the /etc/wpa_supplicant/<name>.conf file. Assuming that your distro is also relatively modern (i.e. uses systemd rather than sysvinit) you should also have systemd-networkd available, which is simple to configure.
When checking into Linux items, my general go-to is the ArchWiki. It's comprehensive, generally presents multiple use cases, and is pretty no-nonsense:
WPA supplicant - ArchWiki
systemd-networkd - ArchWiki
If you want to make your life a bit easier and add some flexibility, you can install NetworkManager:
NetworkManager - ArchWiki
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
|
|
|
|
|
Thanks for reply.
I have been busy trying to find stable OS which actually does WiFi.
What I really need is to know how the whole communication process starts.
During my research I found this gem "wpa_supplicant is build by OS , copied to /etc/... and deleted..." When I try to simply implement "standard" WiFi I actually received "Wpa_supplicant does not exist ". Not much help there.
That is why I ask "who is on first"
Actually I like to use "bonding" so I do not have to worry which type of network I'll am using.
But I really need to hit the books first.
|
|
|
|