Proctor L2127

SimpleLevel = viva difficulty band. Level 1 usually demo + basics; higher pe live coding + deeper theory.

Viva tipJo level assign hai uske hisaab se demo + theory ready rakho.

SimpleViva wrap-up hai. Short thanks + confirm submission ZIP latest hai.

SimpleGitHub repo open karo: commits, collaborators, README. Examiner check karta hai tumne khud kaam kiya.

Example

Settings → Collaborators
Commits: regular messages, last-day dump nahi.

Viva tipPrivate repo access pehle de do. Main branch submitted ZIP se match honi chahiye.

Simplevenv activate → dependencies → DB create/migrate → flask run. Browser pe localhost dikhao.

Example

python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
flask run

SimpleInt column mein string daalne pe SQLAlchemy/DB type error ya Integrity/StatementError. Empty table pe bhi same validation fail — row count matter nahi.

Example

# SQLite may coerce sometimes; Postgres: invalid input syntax for integer
Spot(status='free', lot_id='abc')  # lot_id int → error

SimpleViva wrap-up hai. Short thanks + confirm submission ZIP latest hai.

SimpleCache = pehli baar hisaab karke copy rakh lo, doosri baar copy dikha do.

Baar-baar same expensive kaam (DB query, counting bookings) mat karo. Result Redis jaise store mein timeout ke saath rakh do.

Cache hit: key mil gayi, DB skip. Cache miss: DB se lao, SET karo, return karo.

Tradeoff: speed vs stale data. Admin naya venue add kare aur cache 50s ka ho to user purani list dekh sakta hai — isliye write pe invalidation zaroori hai.

Browser cache, Flask-Caching, Redis alag layers hain. MAD2 examiner Redis + @cache.cached code dekhta hai.

Example

@cache.cached(timeout=50, query_string=True)
@app.route('/api/shows')
def shows():
    return jsonify([s.serialize() for s in Show.query.all()])

Project example: Admin dashboard counts / venues list cache. Create/update/delete ke baad cache.delete('venues').

Viva tipprint('DB queried') function ke andar laga ke miss/hit demo karo — hit pe print nahi chalega.

SimpleVue = UI ka smart assistant. Data badlo, screen khud update. MAD1 Jinja har click pe naya HTML.

Progressive frontend framework. Components, reactivity, directives.

MAD2 SPA: ek index.html, Vue Router pages, Flask sirf JSON.

Fayde: easy, SFC, docs. Vs React: templates HTML-like, course sikhata hai. Vs plain JS: baar-baar DOM mat chhedo.

Example

<!-- HelloWorld.vue -->
<template>
  <h1>{{ msg }}</h1>
</template>
<script>
export default { data() { return { msg: 'Hello' } } }
</script>

Project example: Navbar.vue + views (Login, Dashboard). data() / setup() reactive. fetch APIs.

Viva tipFayde: easy, SFC, reactivity. Vs React: chhota learning curve. Vs plain JS: UI state auto-update.

SimplePehle 1-line definition, phir apne MAD1 project mein file dikhao, phir chhota example.

Suggested flow1) Concept kya hai?
2) Mere code mein kahan?
3) Example / demo
4) Edge case

Example

# related file: models.py / routes / template
# formula: request → check/auth → DB → render/redirect

Viva tipExact line yaad nahi to honestly related part dikhao. Bluff mat karo.

Simplelazy loading: related objects kab load hon. lazy=True default (access pe query). joined/eager pehle se join.

SimpleRedis box hai, Celery us box se kaam uthane wala worker hai — same cheez nahi.

Redis: store (cache keys) + queue (broker lists).
Celery: Python library jo tasks define karti hai, .delay() se queue mein daalti hai, worker execute karta hai.

Dono localhost pe ho sakte hain. Alag Redis DB index use karo. Redis band = cache miss + Celery stuck.

Example

Celery: broker_url='redis://localhost:6379/0'
Cache:  CACHE_REDIS_URL='redis://localhost:6379/1'

Project example: export_csv.delay(user_id) Flask se. Worker Redis se task uthata hai, CSV+email. Cache alag keys venues.

Viva tipAgar possible ho to cache db=1, broker db=0 — keys mix nahi hoti.