Viva Prep

SimpleVue.js frontend framework — reactive UI components. MAD2 mein common, MAD1 optional.

Component: reusable UI (Navbar.vue) + data + template.
Props: parent → child data. Child → parent: $emit('update', val).
Slots: parent child ke andar extra HTML daal sakta hai.
Lifecycle: created (data setup), mounted (DOM ready — API call), updated, unmounted.
v-model two-way bind. Vue Router SPA routes (routes.js). Vuex/Pinia global state; mutations sync change, actions async.
Standalone component: khud ke saath compile, parent register kam.

SimpleCDN se Vue script tag, CLI se full project (webpack/vite, SFC).

CDN: <script src='https://unpkg.com/vue@3'></script> — setup 1 minute, MAD2 proto ke liye theek, offline toot sakta hai.
CLI (vue create / Vite): .vue files, components, router, build step. Production apps ke liye better.
Standalone/SFC components CLI/Vite mein milte hain.

SimpleCDN se Vue script tag, CLI se full project (webpack/vite, SFC).

CDN: <script src='https://unpkg.com/vue@3'></script> — setup 1 minute, MAD2 proto ke liye theek, offline toot sakta hai.
CLI (vue create / Vite): .vue files, components, router, build step. Production apps ke liye better.
Standalone/SFC components CLI/Vite mein milte hain.

SimpleVue.js frontend framework — reactive UI components. MAD2 mein common, MAD1 optional.

Component: reusable UI (Navbar.vue) + data + template.
Props: parent → child data. Child → parent: $emit('update', val).
Slots: parent child ke andar extra HTML daal sakta hai.
Lifecycle: created (data setup), mounted (DOM ready — API call), updated, unmounted.
v-model two-way bind. Vue Router SPA routes (routes.js). Vuex/Pinia global state; mutations sync change, actions async.
Standalone component: khud ke saath compile, parent register kam.

Simplev-if element DOM se hataata/jodata hai, v-show sirf CSS display toggle karta hai.

v-if='isAdmin' → false ho to element exist hi nahi. Costly toggle, lekin hidden data DOM mein nahi.
v-show='open' → display:none. Fast toggle, element hamesha DOM mein.

Rare condition: v-if. Bar-bar toggle (dropdown): v-show.

Simplev-bind one-way data → view, v-model two-way (input ke saath sync).

<img v-bind:src='url'> ya <img :src='url'>  — url change to image change, image se url nahi.
<input v-model='email'> — type karo to email variable turant update.

v-model = :value + @input ka shortcut. Forms mein v-model, attributes mein v-bind.

SimpleVue.js frontend framework — reactive UI components. MAD2 mein common, MAD1 optional.

Component: reusable UI (Navbar.vue) + data + template.
Props: parent → child data. Child → parent: $emit('update', val).
Slots: parent child ke andar extra HTML daal sakta hai.
Lifecycle: created (data setup), mounted (DOM ready — API call), updated, unmounted.
v-model two-way bind. Vue Router SPA routes (routes.js). Vuex/Pinia global state; mutations sync change, actions async.
Standalone component: khud ke saath compile, parent register kam.

SimpleVue.js frontend framework — reactive UI components. MAD2 mein common, MAD1 optional.

Component: reusable UI (Navbar.vue) + data + template.
Props: parent → child data. Child → parent: $emit('update', val).
Slots: parent child ke andar extra HTML daal sakta hai.
Lifecycle: created (data setup), mounted (DOM ready — API call), updated, unmounted.
v-model two-way bind. Vue Router SPA routes (routes.js). Vuex/Pinia global state; mutations sync change, actions async.
Standalone component: khud ke saath compile, parent register kam.

SimpleVue.js frontend framework — reactive UI components. MAD2 mein common, MAD1 optional.

Component: reusable UI (Navbar.vue) + data + template.
Props: parent → child data. Child → parent: $emit('update', val).
Slots: parent child ke andar extra HTML daal sakta hai.
Lifecycle: created (data setup), mounted (DOM ready — API call), updated, unmounted.
v-model two-way bind. Vue Router SPA routes (routes.js). Vuex/Pinia global state; mutations sync change, actions async.
Standalone component: khud ke saath compile, parent register kam.

SimpleORM = Object Relational Mapping. Database tables ko Python classes/objects se map karta hai, raw SQL kam likhni padti hai.

Bina ORM: cursor.execute('SELECT * FROM user WHERE id=?', [5])
ORM se: User.query.get(5) ya db.session.get(User, 5)

Example model

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    email = db.Column(db.String(120), unique=True)

FaydePython mein soch sakte ho, SQL injection se protection (parameterized), relationships easy, DB switch thoda aasan.

Nuksaancomplex queries slow/abstract, seekhne ki layer extra, kabhi raw SQL phir bhi chahiye.

MAD1: SQLAlchemy (Flask-SQLAlchemy). Tables db.create_all() ya migrations se banti hain.

SimpleORM = Object Relational Mapping. Database tables ko Python classes/objects se map karta hai, raw SQL kam likhni padti hai.

Bina ORM: cursor.execute('SELECT * FROM user WHERE id=?', [5])
ORM se: User.query.get(5) ya db.session.get(User, 5)

Example model

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    email = db.Column(db.String(120), unique=True)

FaydePython mein soch sakte ho, SQL injection se protection (parameterized), relationships easy, DB switch thoda aasan.

Nuksaancomplex queries slow/abstract, seekhne ki layer extra, kabhi raw SQL phir bhi chahiye.

MAD1: SQLAlchemy (Flask-SQLAlchemy). Tables db.create_all() ya migrations se banti hain.

SimpleORM = Object Relational Mapping. Database tables ko Python classes/objects se map karta hai, raw SQL kam likhni padti hai.

Bina ORM: cursor.execute('SELECT * FROM user WHERE id=?', [5])
ORM se: User.query.get(5) ya db.session.get(User, 5)

Example model

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    email = db.Column(db.String(120), unique=True)

FaydePython mein soch sakte ho, SQL injection se protection (parameterized), relationships easy, DB switch thoda aasan.

Nuksaancomplex queries slow/abstract, seekhne ki layer extra, kabhi raw SQL phir bhi chahiye.

MAD1: SQLAlchemy (Flask-SQLAlchemy). Tables db.create_all() ya migrations se banti hain.

SimpleSQLAlchemy Python ka sabse popular ORM hai. MAD1 mein Flask-SQLAlchemy wrapper use hota hai.

db = SQLAlchemy(app)

class Book(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    title = db.Column(db.String(80), nullable=False)

Operations: db.session.add(obj), .commit(), .delete(obj), Model.query.all(), .filter_by(), .get_or_404(id).
db.Model ek class hai (function nahi). db object engine + session + metadata hold karta hai.

SQLALCHEMY_TRACK_MODIFICATIONS=False extra signals band karta hai, performance warning hatati hai.

SimpleJWT = JSON Web Token — signed string jisme user id/role hota hai. Har request header mein jaata hai. Session server pe store, JWT client pe.

Login → server token deta hai → Authorization: Bearer <token>
Payload: {sub: user_id, role: admin, exp: ...} — padha ja sakta hai, change nahi (signature).
Session: browser cookie, server-rendered Flask ke liye simple.
Token: mobile/Vue SPA, scaling (server memory nahi). Store: memory/httpOnly cookie, localStorage XSS risk.
MAD1 mostly session. Flask-Security session+login, JWT APIs ke liye.

SimplePassword DB mein plain text mat rakho — hash store karo jo reverse nahi hota.

from werkzeug.security import generate_password_hash, check_password_hash
user.password = generate_password_hash(request.form['password'])
check_password_hash(user.password, form_password)

Hashing ≠ encryption. Leak pe bhi original password nahi milta (easy passwords rainbow table se — isliye salt + strong hash).
Column String(200) kyunki hash lamba hota hai. unique=True password pe mat lagao.

SimpleWebSocket do-tarfa live connection, Webhook 'kisi event pe URL hit karo'.

WebSocket: chat, live scores. Connection open rehti hai.
Webhook: payment success pe Stripe tumhari /webhook URL POST karta hai. Connection nahi, ek HTTP call.
MAD1 mein usually nahi hote; REST request-response hota hai.

SimpleCelery background tasks (email, CSV, reports) async chalaata hai. Redis broker/queue + cache.

User 'Export' click → Celery task queue → Redis message → worker CSV banaata hai → user baad mein download.
Saath isliye: Celery ko broker chahiye, Redis tez in-memory. MAD2 topic zyada, MAD1 mein optional.
Priority: task queues/routing. Caching: Redis mein key-value, DB hits kam.
Pub/Sub: publisher channel pe message, subscribers sunte hain — Redis yeh bhi karta hai.

Simpleexaminer UI tweak maangta hai — CSS class ya inline, instantly dikhao.

Button color: <button class='btn btn-success'> ya style='background:#22c55e;color:#fff'
Navbar: navbar-dark bg-success / style='background:yellow' / fixed-bottom se neeche.
Center: .wrap { display:flex; justify-content:center; align-items:center; min-height:100vh; }
text-align:center heading ke liye. Bootstrap: d-flex justify-content-center, mx-auto, text-center.
Hover: .btn:hover { opacity:0.8; transform:scale(1.02); }
Half width: class='col-6' ya width:50%. Row→column: flex-direction:column / col-12 stack.
Login card: card shadow p-4 mx-auto (max-width:400px).
Table header green: th { background:green; color:white; } Bold column: td:nth-child(2){font-weight:bold}
Box shadow: box-shadow: 4px 4px 12px rgba(0,0,0,.3);
Background image: body { background: url('/static/bg.jpg') center/cover; }
Reset button: <button type='reset'>Clear</button>
Move button: ms-auto / position / flex order.
Jinja dashboard heading: <h1>{{ user.name }}'s Dashboard</h1>

Yeh MAD-1 viva question tumhare project ke context se linked hai. Short answer is structure se do:

Pehle 1 line definition/purpose, phir tumhare project ka example, phir chhota code/flow.

Typical Flask flowBrowser request → @app.route controller → SQLAlchemy model/DB → Jinja template response.

Auth: session['user_id'] + role check. CRUD: add/commit, query.all, field update, delete.
Live change maange to: related model → route → template, phir browser refresh karke dikhao.

Example (generic create):
obj = Model(name=request.form.get('name'))

db.session.add(obj); db.session.commit()
return redirect(url_for('list_view'))

Yeh feature demo hai. Account ready rakho, steps bol ke dikhao.

Role ke hisaab login → action (create/approve/book) → DB/UI pe result → edge case (fail when slots=0 / blacklisted).
Do browser windows: admin + user. Search/filter alag se dikhao.
Agar feature nahi hai to sach bolo aur 2 minute mein kaise add karoge (query + template) explain karo.

SimpleCelery background tasks (email, CSV, reports) async chalaata hai. Redis broker/queue + cache.

User 'Export' click → Celery task queue → Redis message → worker CSV banaata hai → user baad mein download.
Saath isliye: Celery ko broker chahiye, Redis tez in-memory. MAD2 topic zyada, MAD1 mein optional.
Priority: task queues/routing. Caching: Redis mein key-value, DB hits kam.
Pub/Sub: publisher channel pe message, subscribers sunte hain — Redis yeh bhi karta hai.

SimpleVue.js frontend framework — reactive UI components. MAD2 mein common, MAD1 optional.

Component: reusable UI (Navbar.vue) + data + template.
Props: parent → child data. Child → parent: $emit('update', val).
Slots: parent child ke andar extra HTML daal sakta hai.
Lifecycle: created (data setup), mounted (DOM ready — API call), updated, unmounted.
v-model two-way bind. Vue Router SPA routes (routes.js). Vuex/Pinia global state; mutations sync change, actions async.
Standalone component: khud ke saath compile, parent register kam.

Examiner code pe ungli rakh ke poochta hai — panic mat karo, 4-line formula bolo.

1) Yeh file/line kya role hai (model / route / template / config)?
2) Input kahan se aata hai (form, URL <id>, session, JSON)?
3) DB pe kya query/write?
4) Output kya (render_template / redirect / jsonify)?

Example

@app.route('/book/<int:id>', methods=['POST']) — logged-in user session se, trek id URL se, Booking add, slots--, redirect history.

Unknown line: imports (request, url_for, flash), decorators, if checks, commit — har keyword ka reason ready rakho.

SimpleDemo script pehle se practice karo, 5-7 minute, saari roles.

Suggested flow

1) Register/login user 2) Admin login — CRUD 3) Approval/blacklist 4) Booking/apply 5) Search 6) Validation edge (slots 0, duplicate) 7) Logout
Bolte-bolte dikhao: 'Yahan overbooking rokta hoon'. Code tab kholna jab poochhein.
Crash ho to debug calmly: terminal error, typo, DB path.
Mandatory features skip mat karna — examiner list tick karta hai.

Yeh feature demo hai. Account ready rakho, steps bol ke dikhao.

Role ke hisaab login → action (create/approve/book) → DB/UI pe result → edge case (fail when slots=0 / blacklisted).
Do browser windows: admin + user. Search/filter alag se dikhao.
Agar feature nahi hai to sach bolo aur 2 minute mein kaise add karoge (query + template) explain karo.

SimpleIndex kitab ki index jaisi — search tez, poori table scan nahi.

email unique=True already index. Composite: db.Index('ix_user_city_age', User.city, User.age)
Zyada indexes writes slow. Search/filter columns pe lagao.

SimpleSQLAlchemy Python ka sabse popular ORM hai. MAD1 mein Flask-SQLAlchemy wrapper use hota hai.

db = SQLAlchemy(app)

class Book(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    title = db.Column(db.String(80), nullable=False)

Operations: db.session.add(obj), .commit(), .delete(obj), Model.query.all(), .filter_by(), .get_or_404(id).
db.Model ek class hai (function nahi). db object engine + session + metadata hold karta hai.

SQLALCHEMY_TRACK_MODIFICATIONS=False extra signals band karta hai, performance warning hatati hai.

SimplePrimary Key table ki main identity hai (ek hi), Unique Key extra unique column ho sakta hai (kai).

PK: NOT NULL + UNIQUE, sirf ek clustered identity. Example: id
Unique: duplicate nahi, lekin NULL allow ho sakta hai. Example: email, username

UNIQUE + NOT NULL + AUTO_INCREMENT PK jaisa behave karta hai, lekin table ki official PK nahi. Relationships/FK generally PK ko refer karti hain.
Isliye alag Primary Key rakhna better hai.

SimplePrimary Key har row ko uniquely identify karti hai. Unique Key bhi unique hoti hai lekin table ki main ID nahi.

id = db.Column(db.Integer, primary_key=True)  # auto increment
email = db.Column(db.String(120), unique=True)

PK: NOT NULL, ek (ya composite). Index automatically.
Record fetch: User.query.get(id) PK se tez.
FK hamesha unique nahi — Many side pe repeat hoti hai. Unique FK = One-to-One.

Simplemodels.py har table ki class hai — columns, PK/FK, relationships. Yeh Model layer hai.

Viva mein file khol ke bolo:
1) Kaunsi classes/tables hain (User, Role-specific, Booking...)
2) Har table ka kaam 1 line
3) Relationships: 1-1 / 1-M / M-M, backref, cascade, lazy
4) Constraints: unique email, nullable, default status

Example skeleton

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    email = db.Column(db.String(120), unique=True, nullable=False)
    role = db.Column(db.String(20), default='user')
    bookings = db.relationship('Booking', backref='user', cascade='all, delete-orphan')

ER diagram: rectangles entities, lines relationships, PK/FK mark. Schema = yahi structure.
Tables create: db.create_all() ya migrations. SQLite file SQL viewer se dikha sakte ho.

SimpleFlask Python ka micro web framework hai — routes, templates, request/response handle karta hai.

from flask import Flask
app = Flask(__name__)
@app.route('/')
def home():
    return 'Hello'
app.run(debug=True)  # default port 5000

__name__ se Flask ko pata chalta hai templates/static kahan se load karni hai. Hataoge to resource paths toot sakte hain.

Faydesimple, flexible, MAD1 syllabus. Nuksaan: bade features (admin, auth) khud jodne padte hain.

app.run() development server start karta hai. Production mein gunicorn/waitress.

Simpleapp = Flask(__name__) app banata hai; if __name__ == '__main__' tabhi server start jab file directly run ho.

app = Flask(__name__)
if __name__ == '__main__':
    app.run(debug=True, port=5000)

__name__ module ka naam. Direct run pe '__main__', import pe filename. Import karoge to server auto-start nahi — tests/blueprints ke liye zaroori.
debug=True: auto-reload + debugger. Production mein band rakho (security).
Port: app.run(port=8000) ya flask run --port 8000. Default 5000. Haan, change ho sakta hai.

SimpleWSGI = Python web server aur Flask app ke beech standard interface.

gunicorn app:app # WSGI server production
Flask ka app.run() development WSGI. Asgi async (FastAPI) alag.

SimpleUserMixin Flask-Login ko batata hai user object kaise treat karna hai (is_authenticated, get_id).

class User(db.Model, UserMixin):
    id = db.Column(db.Integer, primary_key=True)

current_user proxy logged-in user. Initialize: login_user(user) / user_loader callback.
Flask-WTF: Python classes se forms, CSRF, validators. RegisterForm forms.py mein.
fs_uniquifier Flask-Security mein token/session identity — email change pe sessions invalidate.
enctype='multipart/form-data' file upload pe zaroori. request.files.get('resume').

Simple@login_required / custom decorator check karta hai session mein user hai ya nahi, nahi to login pe bhejta hai.

def login_required(f):
    @wraps(f)
    def wrapper(*a, **k):
        if 'user_id' not in session:
            return redirect(url_for('login'))
        return f(*a, **k)
    return wrapper

@app.before_request se bhi global check ho sakta hai.

Decorator order: pehle @app.route, uske neeche @login_required generally. Swap karoge to kabhi route register galat ho sakta hai — Flask-Login docs follow karo.
Role decorator @role_required('admin') authorization ke liye. Order matter karta hai: pehle auth, phir role.

Definition style question: 1 line simple Hinglish + project example + mini code.

Template'X ka kaam Y hai. Mere project mein Z jagah use hua.'

Example'Session login state rakhta hai. session[user_id]=u.id login pe, logout pe session.clear().'

Agar topic Vue/Celery/Redis ho aur project mein nahi hai to sach bolo, theory example do.

SimpleCelery background tasks (email, CSV, reports) async chalaata hai. Redis broker/queue + cache.

User 'Export' click → Celery task queue → Redis message → worker CSV banaata hai → user baad mein download.
Saath isliye: Celery ko broker chahiye, Redis tez in-memory. MAD2 topic zyada, MAD1 mein optional.
Priority: task queues/routing. Caching: Redis mein key-value, DB hits kam.
Pub/Sub: publisher channel pe message, subscribers sunte hain — Redis yeh bhi karta hai.

Simplejson.dumps Python object ko JSON string banata hai, jsonify Flask Response banata hai (header ke saath).

json.dumps({'ok': True}) → '{"ok": true}' (sirf string)

jsonify(ok=True) → HTTP response, Content-Type: application/json

API route mein jsonify use karo:
@app.route('/api/users')
def users():
    return jsonify([{'id': u.id, 'name': u.name} for u in User.query.all()])

json.dumps se return karoge to browser ise text samajh sakta hai, JSON nahi.

SimpleJSON = JavaScript Object Notation — data exchange ka text format.

{"name": "Ram", "age": 20}
APIs, localStorage, Chart.js data. Python dict ↔ JSON.
Structured data: tables, fixed schema (SQL). Unstructured: images, logs, free text. JSON semi-structured.
SQL structured relational. Mongo unstructured/document.

Simplejson.dumps Python object ko JSON string banata hai, jsonify Flask Response banata hai (header ke saath).

json.dumps({'ok': True}) → '{"ok": true}' (sirf string)

jsonify(ok=True) → HTTP response, Content-Type: application/json

API route mein jsonify use karo:
@app.route('/api/users')
def users():
    return jsonify([{'id': u.id, 'name': u.name} for u in User.query.all()])

json.dumps se return karoge to browser ise text samajh sakta hai, JSON nahi.

SimpleWebSocket do-tarfa live connection, Webhook 'kisi event pe URL hit karo'.

WebSocket: chat, live scores. Connection open rehti hai.
Webhook: payment success pe Stripe tumhari /webhook URL POST karta hai. Connection nahi, ek HTTP call.
MAD1 mein usually nahi hote; REST request-response hota hai.

SimpleVue.js frontend framework — reactive UI components. MAD2 mein common, MAD1 optional.

Component: reusable UI (Navbar.vue) + data + template.
Props: parent → child data. Child → parent: $emit('update', val).
Slots: parent child ke andar extra HTML daal sakta hai.
Lifecycle: created (data setup), mounted (DOM ready — API call), updated, unmounted.
v-model two-way bind. Vue Router SPA routes (routes.js). Vuex/Pinia global state; mutations sync change, actions async.
Standalone component: khud ke saath compile, parent register kam.

SimpleVue.js frontend framework — reactive UI components. MAD2 mein common, MAD1 optional.

Component: reusable UI (Navbar.vue) + data + template.
Props: parent → child data. Child → parent: $emit('update', val).
Slots: parent child ke andar extra HTML daal sakta hai.
Lifecycle: created (data setup), mounted (DOM ready — API call), updated, unmounted.
v-model two-way bind. Vue Router SPA routes (routes.js). Vuex/Pinia global state; mutations sync change, actions async.
Standalone component: khud ke saath compile, parent register kam.

SimpleSearch box GET form, backend query filter, results template mein.

q = request.args.get('q', '').strip()
results = Doctor.query.filter(Doctor.name.ilike(f'%{q}%')).all() if q else []
return render_template('search.html', results=results, q=q)

Jinja: {{ results|length }} matches. Empty: 'No results'.
JS-only filter: saara data pehle load, client filter — chhote lists. Bada data: server search.
Search generally GET (shareable URL). Count: len(results) ya db.func.count.

SimpleDemo script pehle se practice karo, 5-7 minute, saari roles.

Suggested flow

1) Register/login user 2) Admin login — CRUD 3) Approval/blacklist 4) Booking/apply 5) Search 6) Validation edge (slots 0, duplicate) 7) Logout
Bolte-bolte dikhao: 'Yahan overbooking rokta hoon'. Code tab kholna jab poochhein.
Crash ho to debug calmly: terminal error, typo, DB path.
Mandatory features skip mat karna — examiner list tick karta hai.

Yeh feature demo hai. Account ready rakho, steps bol ke dikhao.

Role ke hisaab login → action (create/approve/book) → DB/UI pe result → edge case (fail when slots=0 / blacklisted).
Do browser windows: admin + user. Search/filter alag se dikhao.
Agar feature nahi hai to sach bolo aur 2 minute mein kaise add karoge (query + template) explain karo.

Simple2-3 honest improvements + 1 security + 1 UX.

Example

password hashing/CSRF tighter, Redis cache, tests, pagination, email verify, rate limit login, better mobile CSS.

Challenges: relationships/cascade, concurrent booking, Jinja inheritance.
Rate: 7-8/10 with reason — 10/10 arrogant, 3/10 confidence khatam.
Security extra: HTTPS, hashed passwords, CSRF, SQL injection (ORM), login attempts, file type check.

SimpleDemo script pehle se practice karo, 5-7 minute, saari roles.

Suggested flow

1) Register/login user 2) Admin login — CRUD 3) Approval/blacklist 4) Booking/apply 5) Search 6) Validation edge (slots 0, duplicate) 7) Logout
Bolte-bolte dikhao: 'Yahan overbooking rokta hoon'. Code tab kholna jab poochhein.
Crash ho to debug calmly: terminal error, typo, DB path.
Mandatory features skip mat karna — examiner list tick karta hai.

SimpleRoutes/controllers URLs handle karte hain. app.py app banata hai, models.py data, templates/ views, static/ CSS-JS.

Typical structure:
app.py / __init__.py → Flask app, db.init, register blueprints
models.py → tables
routes.py / views → @app.route functions
templates/ → Jinja HTML
static/ → css, images
instance/*.db → SQLite

Ek route explain karne ka template:
1) URL + methods 2) Auth/role check 3) Form/query se data 4) Business rule (duplicate, slots) 5) db.session 6) render ya redirect

Example GET+POST same route: GET form, POST save.
Data HTML se: form name= → request.form. Data HTML ko: render_template(..., items=query).
Nayi .py file: import karke use karo, warna Flask ko pata nahi. Folder rename: imports/paths/templates check.

SimpleDemo script pehle se practice karo, 5-7 minute, saari roles.

Suggested flow

1) Register/login user 2) Admin login — CRUD 3) Approval/blacklist 4) Booking/apply 5) Search 6) Validation edge (slots 0, duplicate) 7) Logout
Bolte-bolte dikhao: 'Yahan overbooking rokta hoon'. Code tab kholna jab poochhein.
Crash ho to debug calmly: terminal error, typo, DB path.
Mandatory features skip mat karna — examiner list tick karta hai.

SimpleRoutes/controllers URLs handle karte hain. app.py app banata hai, models.py data, templates/ views, static/ CSS-JS.

Typical structure:
app.py / __init__.py → Flask app, db.init, register blueprints
models.py → tables
routes.py / views → @app.route functions
templates/ → Jinja HTML
static/ → css, images
instance/*.db → SQLite

Ek route explain karne ka template:
1) URL + methods 2) Auth/role check 3) Form/query se data 4) Business rule (duplicate, slots) 5) db.session 6) render ya redirect

Example GET+POST same route: GET form, POST save.
Data HTML se: form name= → request.form. Data HTML ko: render_template(..., items=query).
Nayi .py file: import karke use karo, warna Flask ko pata nahi. Folder rename: imports/paths/templates check.

Simplemodels.py har table ki class hai — columns, PK/FK, relationships. Yeh Model layer hai.

Viva mein file khol ke bolo:
1) Kaunsi classes/tables hain (User, Role-specific, Booking...)
2) Har table ka kaam 1 line
3) Relationships: 1-1 / 1-M / M-M, backref, cascade, lazy
4) Constraints: unique email, nullable, default status

Example skeleton

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    email = db.Column(db.String(120), unique=True, nullable=False)
    role = db.Column(db.String(20), default='user')
    bookings = db.relationship('Booking', backref='user', cascade='all, delete-orphan')

ER diagram: rectangles entities, lines relationships, PK/FK mark. Schema = yahi structure.
Tables create: db.create_all() ya migrations. SQLite file SQL viewer se dikha sakte ho.

SimpleRoutes/controllers URLs handle karte hain. app.py app banata hai, models.py data, templates/ views, static/ CSS-JS.

Typical structure:
app.py / __init__.py → Flask app, db.init, register blueprints
models.py → tables
routes.py / views → @app.route functions
templates/ → Jinja HTML
static/ → css, images
instance/*.db → SQLite

Ek route explain karne ka template:
1) URL + methods 2) Auth/role check 3) Form/query se data 4) Business rule (duplicate, slots) 5) db.session 6) render ya redirect

Example GET+POST same route: GET form, POST save.
Data HTML se: form name= → request.form. Data HTML ko: render_template(..., items=query).
Nayi .py file: import karke use karo, warna Flask ko pata nahi. Folder rename: imports/paths/templates check.

Simplemodels.py har table ki class hai — columns, PK/FK, relationships. Yeh Model layer hai.

Viva mein file khol ke bolo:
1) Kaunsi classes/tables hain (User, Role-specific, Booking...)
2) Har table ka kaam 1 line
3) Relationships: 1-1 / 1-M / M-M, backref, cascade, lazy
4) Constraints: unique email, nullable, default status

Example skeleton

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    email = db.Column(db.String(120), unique=True, nullable=False)
    role = db.Column(db.String(20), default='user')
    bookings = db.relationship('Booking', backref='user', cascade='all, delete-orphan')

ER diagram: rectangles entities, lines relationships, PK/FK mark. Schema = yahi structure.
Tables create: db.create_all() ya migrations. SQLite file SQL viewer se dikha sakte ho.

Examiner code pe ungli rakh ke poochta hai — panic mat karo, 4-line formula bolo.

1) Yeh file/line kya role hai (model / route / template / config)?
2) Input kahan se aata hai (form, URL <id>, session, JSON)?
3) DB pe kya query/write?
4) Output kya (render_template / redirect / jsonify)?

Example

@app.route('/book/<int:id>', methods=['POST']) — logged-in user session se, trek id URL se, Booking add, slots--, redirect history.

Unknown line: imports (request, url_for, flash), decorators, if checks, commit — har keyword ka reason ready rakho.

SimpleSearch box GET form, backend query filter, results template mein.

q = request.args.get('q', '').strip()
results = Doctor.query.filter(Doctor.name.ilike(f'%{q}%')).all() if q else []
return render_template('search.html', results=results, q=q)

Jinja: {{ results|length }} matches. Empty: 'No results'.
JS-only filter: saara data pehle load, client filter — chhote lists. Bada data: server search.
Search generally GET (shareable URL). Count: len(results) ya db.func.count.

SimpleSearch box GET form, backend query filter, results template mein.

q = request.args.get('q', '').strip()
results = Doctor.query.filter(Doctor.name.ilike(f'%{q}%')).all() if q else []
return render_template('search.html', results=results, q=q)

Jinja: {{ results|length }} matches. Empty: 'No results'.
JS-only filter: saara data pehle load, client filter — chhote lists. Bada data: server search.
Search generally GET (shareable URL). Count: len(results) ya db.func.count.

SimpleRBAC = Role-Based Access Control — permission role se (admin/staff/user), har user pe alag nahi.

user.role = 'admin'
if current_user.role != 'admin': abort(403)

Same login page, role ke hisaab dashboard. Multiple roles: roles table Many-to-Many, ya comma field (behtar normalized table).
Unapproved staff: is_approved flag, login pe check.
Flask-Security/UserMixin is_authenticated, is_active, get_id dete hain.

SimpleFile upload form multipart, Flask request.files, disk ya DB path store.

<form method='POST' enctype='multipart/form-data'>
f = request.files.get('resume')
f.save(os.path.join('uploads', secure_filename(f.filename)))

Sensitive docs uploads/ web se seedha serve mat karo, login check ke baad send_from_directory.
Student resume edit: policy — allowed hai to Update route, nahi to freeze after apply.

Examiner code pe ungli rakh ke poochta hai — panic mat karo, 4-line formula bolo.

1) Yeh file/line kya role hai (model / route / template / config)?
2) Input kahan se aata hai (form, URL <id>, session, JSON)?
3) DB pe kya query/write?
4) Output kya (render_template / redirect / jsonify)?

Example

@app.route('/book/<int:id>', methods=['POST']) — logged-in user session se, trek id URL se, Booking add, slots--, redirect history.

Unknown line: imports (request, url_for, flash), decorators, if checks, commit — har keyword ka reason ready rakho.

SimpleLogin GET form dikhata hai, POST credentials check karke session set karta hai.

@app.route('/login', methods=['GET','POST'])
def login():
    if request.method == 'POST':
        u = User.query.filter_by(email=request.form.get('email')).first()
        if u and check_password_hash(u.password, request.form.get('password')):
            if getattr(u, 'blacklisted', False):
                flash('Blocked'); return redirect(url_for('login'))
            session['user_id'] = u.id
            session['role'] = u.role
            return redirect(url_for('dashboard'))
        flash('Invalid')
    return render_template('login.html')

Logout: session.clear(); redirect login. Incognito alag cookie jar — logged out dikhega.
Single login page: role se redirect alag dashboards.

SimpleRoutes/controllers URLs handle karte hain. app.py app banata hai, models.py data, templates/ views, static/ CSS-JS.

Typical structure:
app.py / __init__.py → Flask app, db.init, register blueprints
models.py → tables
routes.py / views → @app.route functions
templates/ → Jinja HTML
static/ → css, images
instance/*.db → SQLite

Ek route explain karne ka template:
1) URL + methods 2) Auth/role check 3) Form/query se data 4) Business rule (duplicate, slots) 5) db.session 6) render ya redirect

Example GET+POST same route: GET form, POST save.
Data HTML se: form name= → request.form. Data HTML ko: render_template(..., items=query).
Nayi .py file: import karke use karo, warna Flask ko pata nahi. Folder rename: imports/paths/templates check.

SimpleRoutes/controllers URLs handle karte hain. app.py app banata hai, models.py data, templates/ views, static/ CSS-JS.

Typical structure:
app.py / __init__.py → Flask app, db.init, register blueprints
models.py → tables
routes.py / views → @app.route functions
templates/ → Jinja HTML
static/ → css, images
instance/*.db → SQLite

Ek route explain karne ka template:
1) URL + methods 2) Auth/role check 3) Form/query se data 4) Business rule (duplicate, slots) 5) db.session 6) render ya redirect

Example GET+POST same route: GET form, POST save.
Data HTML se: form name= → request.form. Data HTML ko: render_template(..., items=query).
Nayi .py file: import karke use karo, warna Flask ko pata nahi. Folder rename: imports/paths/templates check.

Examiner code pe ungli rakh ke poochta hai — panic mat karo, 4-line formula bolo.

1) Yeh file/line kya role hai (model / route / template / config)?
2) Input kahan se aata hai (form, URL <id>, session, JSON)?
3) DB pe kya query/write?
4) Output kya (render_template / redirect / jsonify)?

Example

@app.route('/book/<int:id>', methods=['POST']) — logged-in user session se, trek id URL se, Booking add, slots--, redirect history.

Unknown line: imports (request, url_for, flash), decorators, if checks, commit — har keyword ka reason ready rakho.

Examiner code pe ungli rakh ke poochta hai — panic mat karo, 4-line formula bolo.

1) Yeh file/line kya role hai (model / route / template / config)?
2) Input kahan se aata hai (form, URL <id>, session, JSON)?
3) DB pe kya query/write?
4) Output kya (render_template / redirect / jsonify)?

Example

@app.route('/book/<int:id>', methods=['POST']) — logged-in user session se, trek id URL se, Booking add, slots--, redirect history.

Unknown line: imports (request, url_for, flash), decorators, if checks, commit — har keyword ka reason ready rakho.

SimpleForm user input server ko bhejti hai. Table rows/columns dikhati hai.

<form action="{{ url_for('register') }}" method='POST' enctype='multipart/form-data'>
  <input name='email' required>
  <button type='submit'>Go</button>
</form>

name attribute server pe key ban'ti hai: request.form['email']. id JS/CSS, value default/dikhta hua text.
action URL. method GET/POST. enctype file upload pe multipart.
required frontend empty submit rokta hai (backend phir bhi check).

<table><thead><tr><th>Name</th></tr></thead><tbody><tr><td>{{ u.name }}</td></tr></tbody></table>

th header, td data, tr row. Nested table: td ke andar table (avoid, messy).
method hataoge to GET, password URL mein — buri baat.

Simple 4-step: Model → DB → Form → Route → Template. Yeh sabse common live-coding hai.

1) models.py: age = db.Column(db.Integer, nullable=True)
2) DB: SQLite viewer se column, ya DB delete karke create_all, ya ALTER TABLE user ADD COLUMN age INTEGER; production mein Flask-Migrate.
3) register.html: <input type='number' name='age' min='18' required>
4) route: user.age = request.form.get('age', type=int); commit
5) dashboard: {{ user.age }} admin table mein <td>{{ u.age }}</td>

Print terminal: print('AGE', request.form.get('age'))
Phone/city same pattern, String(20). Openings on Drive: integer column + form + create_drive route.

SimpleValidation galat data rok ti hai — frontend turant, backend must.

Frontend: required, min='18', maxlength='8', pattern='(?=.*[A-Z]).{8,}'
Backend example:

pwd = request.form.get('password','')
if len(pwd) < 8 or not re.search(r'[A-Z]', pwd) or not re.search(r'[0-9]', pwd):
    flash('Weak password')

Haan, regex se password rules ho sakte hain.
Age 18-99, date >= today, slots <= 30 and > 0, confirm password == password, email '@' .
Duplicate username: User.query.filter_by(email=email).first() or unique=True catch IntegrityError.
Past date: if date < date.today(): reject. Negative slots: if slots < 0: reject; book pe available > 0 check.

SimpleValidation galat data rok ti hai — frontend turant, backend must.

Frontend: required, min='18', maxlength='8', pattern='(?=.*[A-Z]).{8,}'
Backend example:

pwd = request.form.get('password','')
if len(pwd) < 8 or not re.search(r'[A-Z]', pwd) or not re.search(r'[0-9]', pwd):
    flash('Weak password')

Haan, regex se password rules ho sakte hain.
Age 18-99, date >= today, slots <= 30 and > 0, confirm password == password, email '@' .
Duplicate username: User.query.filter_by(email=email).first() or unique=True catch IntegrityError.
Past date: if date < date.today(): reject. Negative slots: if slots < 0: reject; book pe available > 0 check.

Simple 4-step: Model → DB → Form → Route → Template. Yeh sabse common live-coding hai.

1) models.py: age = db.Column(db.Integer, nullable=True)
2) DB: SQLite viewer se column, ya DB delete karke create_all, ya ALTER TABLE user ADD COLUMN age INTEGER; production mein Flask-Migrate.
3) register.html: <input type='number' name='age' min='18' required>
4) route: user.age = request.form.get('age', type=int); commit
5) dashboard: {{ user.age }} admin table mein <td>{{ u.age }}</td>

Print terminal: print('AGE', request.form.get('age'))
Phone/city same pattern, String(20). Openings on Drive: integer column + form + create_drive route.

Simple 4-step: Model → DB → Form → Route → Template. Yeh sabse common live-coding hai.

1) models.py: age = db.Column(db.Integer, nullable=True)
2) DB: SQLite viewer se column, ya DB delete karke create_all, ya ALTER TABLE user ADD COLUMN age INTEGER; production mein Flask-Migrate.
3) register.html: <input type='number' name='age' min='18' required>
4) route: user.age = request.form.get('age', type=int); commit
5) dashboard: {{ user.age }} admin table mein <td>{{ u.age }}</td>

Print terminal: print('AGE', request.form.get('age'))
Phone/city same pattern, String(20). Openings on Drive: integer column + form + create_drive route.

Yeh project-specific feature add/modify hai. 4 layers touch karo: model, route, template, validation.

1) Data chahiye to models.py mein column/relationship + DB update (ALTER / migrate / create_all).
2) Route: GET pe form/page, POST pe request.form se save, flash + redirect.
3) Template: input name=... Jinja se {{ obj.field }} display.
4) Rule: duplicate, range, role check backend pe.

Example naya field 'city':

user.city = db.Column(db.String(50))
user.city = request.form.get('city')
<input name='city'>  ...  {{ user.city }}

SimpleValidation galat data rok ti hai — frontend turant, backend must.

Frontend: required, min='18', maxlength='8', pattern='(?=.*[A-Z]).{8,}'
Backend example:

pwd = request.form.get('password','')
if len(pwd) < 8 or not re.search(r'[A-Z]', pwd) or not re.search(r'[0-9]', pwd):
    flash('Weak password')

Haan, regex se password rules ho sakte hain.
Age 18-99, date >= today, slots <= 30 and > 0, confirm password == password, email '@' .
Duplicate username: User.query.filter_by(email=email).first() or unique=True catch IntegrityError.
Past date: if date < date.today(): reject. Negative slots: if slots < 0: reject; book pe available > 0 check.

Yeh live UI/CSS change hai. Examiner jo element bole uski CSS turant badlo.

Bootstrap class badlo (btn-primary → btn-success, bg-dark → bg-warning) ya inline style='color:red; background:#eee'.
Center: d-flex justify-content-center text-center. Navbar neeche: navbar fixed-bottom.

Example

<button class='btn btn-success' style='background:#16a34a'>Book</button>

Pehle browser inspect karke class dhundo, phir template mein change karke refresh.

Yeh live UI/CSS change hai. Examiner jo element bole uski CSS turant badlo.

Bootstrap class badlo (btn-primary → btn-success, bg-dark → bg-warning) ya inline style='color:red; background:#eee'.
Center: d-flex justify-content-center text-center. Navbar neeche: navbar fixed-bottom.

Example

<button class='btn btn-success' style='background:#16a34a'>Book</button>

Pehle browser inspect karke class dhundo, phir template mein change karke refresh.

Yeh MAD-1 viva question tumhare project ke context se linked hai. Short answer is structure se do:

Pehle 1 line definition/purpose, phir tumhare project ka example, phir chhota code/flow.

Typical Flask flowBrowser request → @app.route controller → SQLAlchemy model/DB → Jinja template response.

Auth: session['user_id'] + role check. CRUD: add/commit, query.all, field update, delete.
Live change maange to: related model → route → template, phir browser refresh karke dikhao.

Example (generic create):
obj = Model(name=request.form.get('name'))

db.session.add(obj); db.session.commit()
return redirect(url_for('list_view'))

SimpleValidation galat data rok ti hai — frontend turant, backend must.

Frontend: required, min='18', maxlength='8', pattern='(?=.*[A-Z]).{8,}'
Backend example:

pwd = request.form.get('password','')
if len(pwd) < 8 or not re.search(r'[A-Z]', pwd) or not re.search(r'[0-9]', pwd):
    flash('Weak password')

Haan, regex se password rules ho sakte hain.
Age 18-99, date >= today, slots <= 30 and > 0, confirm password == password, email '@' .
Duplicate username: User.query.filter_by(email=email).first() or unique=True catch IntegrityError.
Past date: if date < date.today(): reject. Negative slots: if slots < 0: reject; book pe available > 0 check.

SimpleDuplicate/overbook rokne ke liye DB constraint + route check dono.

Pehle query: Booking.query.filter_by(user_id=uid, trek_id=tid).first()
Agar exists: flash('Already booked'); return
Slots: if trek.available <= 0: reject else trek.available -= 1; commit
Race condition: unique(user_id, trek_id) constraint — do tabs se double click pe bhi ek hi row.
Blacklist: login pe is_blacklisted check.
Active drive limit: if Company ke paas status=open drive hai to naya mat banne do.

SimplePassword DB mein plain text mat rakho — hash store karo jo reverse nahi hota.

from werkzeug.security import generate_password_hash, check_password_hash
user.password = generate_password_hash(request.form['password'])
check_password_hash(user.password, form_password)

Hashing ≠ encryption. Leak pe bhi original password nahi milta (easy passwords rainbow table se — isliye salt + strong hash).
Column String(200) kyunki hash lamba hota hai. unique=True password pe mat lagao.

SimplePassword DB mein plain text mat rakho — hash store karo jo reverse nahi hota.

from werkzeug.security import generate_password_hash, check_password_hash
user.password = generate_password_hash(request.form['password'])
check_password_hash(user.password, form_password)

Hashing ≠ encryption. Leak pe bhi original password nahi milta (easy passwords rainbow table se — isliye salt + strong hash).
Column String(200) kyunki hash lamba hota hai. unique=True password pe mat lagao.

Simplebackref relationship ki reverse side automatically bana deta hai.

class Post(db.Model):
    user_id = db.Column(db.Integer, db.ForeignKey('user.id'))
    user = db.relationship('User', backref='posts')

Ab post.user milta hai, aur user.posts bhi — Post model pe sirf ek line.
secondary Many-to-Many junction table ke liye: relationship(..., secondary=likes_table, backref='liked_by').
Explicit chahiye to back_populates use karo.

Simpleback_populates dono models pe relationship explicitly link karta hai.

class User(db.Model):
    posts = db.relationship('Post', back_populates='author')
class Post(db.Model):
    author = db.relationship('User', back_populates='posts')

Naam match hona chahiye. Readability better, circular confusion kam. backref ka alternative yahi hai.

Simpledono SQLAlchemy relationships ko do taraf se connect karte hain, farq sirf likhne ke style ka hai.

backref: relationship ek side pe likhte ho, doosri side SQLAlchemy khud bana deta hai. Short hai, lekin dono models dekh ke relationship clearly nahi dikhti.

back_populates: dono models pe relationship explicitly likhte ho. Code padhne wale ko turant samajh aa jaata hai ki User.posts aur Post.author linked hain.

Example

class User(db.Model):
    posts = db.relationship('Post', backref='author')

Yahan Post.author automatically mil jaata hai.

Explicit version:

class User(db.Model):
    posts = db.relationship('Post', back_populates='author')
class Post(db.Model):
    author = db.relationship('User', back_populates='posts')

Viva tipexaminer ko bolo — MAD1 project mein back_populates zyada clear hai, isliye preferred.

SimpleRelationships tables ko jodti hain taaki related data object se mil jaaye.

One-to-Many: User → kai Posts. posts = relationship('Post', backref='author'). FK post.user_id.
One-to-One: User → Profile. uselist=False + unique FK. Profile.user_id unique.
Many-to-Many: Student ↔ Drive. Junction/secondary table (student_id, drive_id).

Example 1-1:

class Profile(db.Model):
    user_id = db.Column(db.Integer, db.ForeignKey('user.id'), unique=True)
    user = db.relationship('User', back_populates='profile', uselist=False)

1-M ko 1-1: child FK pe unique=True + uselist=False.
Parent-child: parent PK, child FK. Junction table extra columns bhi rakh sakti hai (applied_on).

Simplelazy loading related objects tab load karta hai jab attribute access karte ho, pehle nahi.

user = User.query.get(1)  # posts query nahi

user.posts # ab query

lazy=True / 'select' default. lazy='joined' eager join. lazy='dynamic' query object.
uselist=False One-to-One (single object, list nahi). Hataoge to list mil sakti hai.
Frontend lazy loading images alag cheez hai (viewport mein aaye tab load).

Examiner code pe ungli rakh ke poochta hai — panic mat karo, 4-line formula bolo.

1) Yeh file/line kya role hai (model / route / template / config)?
2) Input kahan se aata hai (form, URL <id>, session, JSON)?
3) DB pe kya query/write?
4) Output kya (render_template / redirect / jsonify)?

Example

@app.route('/book/<int:id>', methods=['POST']) — logged-in user session se, trek id URL se, Booking add, slots--, redirect history.

Unknown line: imports (request, url_for, flash), decorators, if checks, commit — har keyword ka reason ready rakho.

SimpleCascade parent ke saath child pe automatic action (generally delete).

Company delete → uski drives bhi delete, warna orphan rows / FK error.
SQLAlchemy: db.relationship('Drive', cascade='all, delete-orphan', backref='company')
SQL: ForeignKey(..., ondelete='CASCADE')

Cascade sirf delete nahi: save-update, merge, refresh-expire, expunge, delete-orphan.
Cascade Update: parent PK change to child FK update (rare, PK mat badlo).
Parent delete jab children active hon: constraint error, ya cascade se children gayab, ya pehle children handle karo — design choice examiner poochta hai.
CSS cascading alag topic hai (styles inherit/override).

SimpleForeign Key doosri table ki PK ko refer karti hai, relationship + referential integrity.

user_id = db.Column(db.Integer, db.ForeignKey('user.id'), nullable=False)

Invalid user_id insert nahi hoga. FK unique nahi hona zaroori — One-to-Many mein same user_id kai rows.
FK + PK same column: 1-1 sharing, jaise AdminProfile.id = FK to user.id.
Should FK always unique? Nahi. Tab One-to-One chahiye ho tab unique.

SimpleForeign Key doosri table ki PK ko refer karti hai, relationship + referential integrity.

user_id = db.Column(db.Integer, db.ForeignKey('user.id'), nullable=False)

Invalid user_id insert nahi hoga. FK unique nahi hona zaroori — One-to-Many mein same user_id kai rows.
FK + PK same column: 1-1 sharing, jaise AdminProfile.id = FK to user.id.
Should FK always unique? Nahi. Tab One-to-One chahiye ho tab unique.

SimpleForeign Key doosri table ki PK ko refer karti hai, relationship + referential integrity.

user_id = db.Column(db.Integer, db.ForeignKey('user.id'), nullable=False)

Invalid user_id insert nahi hoga. FK unique nahi hona zaroori — One-to-Many mein same user_id kai rows.
FK + PK same column: 1-1 sharing, jaise AdminProfile.id = FK to user.id.
Should FK always unique? Nahi. Tab One-to-One chahiye ho tab unique.

SimplePrimary Key row ki unique ID hai, Foreign Key doosri table ki Primary Key ko point karti hai.

Primary Key: unique + not null. Har table mein hota hai. Example: user.id = 5
Foreign Key: relationship banati hai. post.user_id = 5 matlab yeh post user 5 ki hai.

Example

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
class Post(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    user_id = db.Column(db.Integer, db.ForeignKey('user.id'))

FK Primary Key bhi ho sakti hai (1-to-1 profile table). FK unique ho to One-to-One, nahi to One-to-Many.

SimpleRelationships tables ko jodti hain taaki related data object se mil jaaye.

One-to-Many: User → kai Posts. posts = relationship('Post', backref='author'). FK post.user_id.
One-to-One: User → Profile. uselist=False + unique FK. Profile.user_id unique.
Many-to-Many: Student ↔ Drive. Junction/secondary table (student_id, drive_id).

Example 1-1:

class Profile(db.Model):
    user_id = db.Column(db.Integer, db.ForeignKey('user.id'), unique=True)
    user = db.relationship('User', back_populates='profile', uselist=False)

1-M ko 1-1: child FK pe unique=True + uselist=False.
Parent-child: parent PK, child FK. Junction table extra columns bhi rakh sakti hai (applied_on).

Simple 4-step: Model → DB → Form → Route → Template. Yeh sabse common live-coding hai.

1) models.py: age = db.Column(db.Integer, nullable=True)
2) DB: SQLite viewer se column, ya DB delete karke create_all, ya ALTER TABLE user ADD COLUMN age INTEGER; production mein Flask-Migrate.
3) register.html: <input type='number' name='age' min='18' required>
4) route: user.age = request.form.get('age', type=int); commit
5) dashboard: {{ user.age }} admin table mein <td>{{ u.age }}</td>

Print terminal: print('AGE', request.form.get('age'))
Phone/city same pattern, String(20). Openings on Drive: integer column + form + create_drive route.

Yeh MAD-1 viva question tumhare project ke context se linked hai. Short answer is structure se do:

Pehle 1 line definition/purpose, phir tumhare project ka example, phir chhota code/flow.

Typical Flask flowBrowser request → @app.route controller → SQLAlchemy model/DB → Jinja template response.

Auth: session['user_id'] + role check. CRUD: add/commit, query.all, field update, delete.
Live change maange to: related model → route → template, phir browser refresh karke dikhao.

Example (generic create):
obj = Model(name=request.form.get('name'))

db.session.add(obj); db.session.commit()
return redirect(url_for('list_view'))

Simpleurl_for sirf URL string banata hai, redirect us URL pe browser ko bhejta hai.

url_for('home') → '/home' (function name se URL nikalta hai)
redirect(url_for('home')) → browser ko /home pe le jaata hai

Example

return redirect(url_for('dashboard'))  # sahi
return redirect('/dashboard')         # hardcode, route change pe toot jaayega

Agar redirect se url_for hata do to khud path string dena padega: redirect('/dashboard').
Agar url_for('home') ko url_for('home_page') kar do aur home_page naam ka function nahi hai to BuildError aayega.

url_for ko function ka naam chahiye, URL path nahi.

Simplerender_template HTML page bana ke turant dikhata hai, redirect user ko doosre URL pe bhej deta hai.

render_template('home.html', user=user) → server template fill karke 200 response deta hai. URL same rehta hai.
redirect(url_for('dashboard')) → 302 response, browser naya GET karta hai. URL change ho jaata hai.

Examplelogin POST successful hone ke baad render_template mat use karo, warna refresh pe form dubara submit ho jaayega.

Sahi tarika: redirect(url_for('dashboard')) — yeh Post-Redirect-Get pattern hai.

render_template tab: page dikhana hai with data.
redirect tab: kaam ho gaya, ab doosre page pe le jaana hai (login, delete, update ke baad).

Simpleurl_for URL nikalta hai, render_template HTML page return karta hai. Dono alag kaam.

url_for('login') → '/login'
render_template('login.html') → login page ka HTML

Templates mein link ke liye: <a href="{{ url_for('dashboard') }}">Dashboard</a>
Route mein page dikhane ke liye: return render_template('dashboard.html', user=user)

url_for endpoint/function name leta hai, render_template HTML file name leta hai.

Simpleextends poora layout inherit karta hai, include chhota piece insert karta hai.

extends: child page base.html ka structure use karti hai, blocks override karti hai. Ek hi parent.
include: navbar.html / footer.html jahan chaho insert. Kai baar use ho sakta hai.

base.html:

{% block content %}{% endblock %}

home.html:
{% extends 'base.html' %}
{% block content %}<h1>Home</h1>{% endblock %}

{% include 'navbar.html' %}  → navbar har page pe

Fayda: header/footer ek jagah, change once — saari pages update. MAD1 mein almost har project use karta hai.

SimpleJinja2 Flask ka template engine hai. HTML ke andar Python-jaisa data print/loop/if kar sakte ho.

Bina Jinja har user ke liye alag HTML file. Jinja se ek template + data.

{{ user.name }} print, {% for x in items %} loop, {% if %} condition, {% extends %} layout.

Example routereturn render_template('dash.html', treks=treks)

dash.html: {% for t in treks %}<li>{{ t.name }}</li>{% endfor %}

HTML files templates/ folder mein isliye kyunki Flask default wahan dhundhta hai. render_template Jinja ko run karta hai.
Boolean Jinja handle karta hai: {% if user.is_admin %}.

Definition style question: 1 line simple Hinglish + project example + mini code.

Template'X ka kaam Y hai. Mere project mein Z jagah use hua.'

Example'Session login state rakhta hai. session[user_id]=u.id login pe, logout pe session.clear().'

Agar topic Vue/Celery/Redis ho aur project mein nahi hai to sach bolo, theory example do.

Simple Jinja loop + if — examiner notepad mein likhwaata hai:

{% for t in treks %}
  <p>{{ t.name }} — {{ t.location }}</p>
{% else %}
  <p>No treks</p>
{% endfor %}

{% if user.role == 'admin' %}
  <button>Delete</button>
{% endif %}

List filter: {% if x > 10 %}{{ x }}{% endif %}
Length: {{ items|length }} Upper: {{ name|upper }}
Table: loop ke andar <tr><td>

Yeh MAD-1 viva question tumhare project ke context se linked hai. Short answer is structure se do:

Pehle 1 line definition/purpose, phir tumhare project ka example, phir chhota code/flow.

Typical Flask flowBrowser request → @app.route controller → SQLAlchemy model/DB → Jinja template response.

Auth: session['user_id'] + role check. CRUD: add/commit, query.all, field update, delete.
Live change maange to: related model → route → template, phir browser refresh karke dikhao.

Example (generic create):
obj = Model(name=request.form.get('name'))

db.session.add(obj); db.session.commit()
return redirect(url_for('list_view'))

SimpleMVC = Model-View-Controller. Code ko 3 hisson mein baant ta hai taaki mix na ho.

Model: data + DB. models.py — User, Trek, Booking classes.
View: jo user dekhta hai. templates/*.html + Jinja.
Controller: beech ka logic. routes / app.py — request lo, model se data, view ko do.

Example flow (register):
Browser form POST → Controller register() → User model save → redirect → View dashboard.html

Draw: Browser → Controller → Model → DB, phir Controller → View → Browser.
ORM na ho to bhi MVC ho sakta hai — Model raw SQL functions ho sakte hain. Structure matter karta hai, library nahi.
MVP/MVVM doosri architectures hain; MAD1 mein MVC expected hai.

SimpleMVC = Model-View-Controller. Code ko 3 hisson mein baant ta hai taaki mix na ho.

Model: data + DB. models.py — User, Trek, Booking classes.
View: jo user dekhta hai. templates/*.html + Jinja.
Controller: beech ka logic. routes / app.py — request lo, model se data, view ko do.

Example flow (register):
Browser form POST → Controller register() → User model save → redirect → View dashboard.html

Draw: Browser → Controller → Model → DB, phir Controller → View → Browser.
ORM na ho to bhi MVC ho sakta hai — Model raw SQL functions ho sakte hain. Structure matter karta hai, library nahi.
MVP/MVVM doosri architectures hain; MAD1 mein MVC expected hai.

Definition style question: 1 line simple Hinglish + project example + mini code.

Template'X ka kaam Y hai. Mere project mein Z jagah use hua.'

Example'Session login state rakhta hai. session[user_id]=u.id login pe, logout pe session.clear().'

Agar topic Vue/Celery/Redis ho aur project mein nahi hai to sach bolo, theory example do.

Yeh MAD-1 viva question tumhare project ke context se linked hai. Short answer is structure se do:

Pehle 1 line definition/purpose, phir tumhare project ka example, phir chhota code/flow.

Typical Flask flowBrowser request → @app.route controller → SQLAlchemy model/DB → Jinja template response.

Auth: session['user_id'] + role check. CRUD: add/commit, query.all, field update, delete.
Live change maange to: related model → route → template, phir browser refresh karke dikhao.

Example (generic create):
obj = Model(name=request.form.get('name'))

db.session.add(obj); db.session.commit()
return redirect(url_for('list_view'))

Yeh MAD-1 viva question tumhare project ke context se linked hai. Short answer is structure se do:

Pehle 1 line definition/purpose, phir tumhare project ka example, phir chhota code/flow.

Typical Flask flowBrowser request → @app.route controller → SQLAlchemy model/DB → Jinja template response.

Auth: session['user_id'] + role check. CRUD: add/commit, query.all, field update, delete.
Live change maange to: related model → route → template, phir browser refresh karke dikhao.

Example (generic create):
obj = Model(name=request.form.get('name'))

db.session.add(obj); db.session.commit()
return redirect(url_for('list_view'))