bigakis

Some notes: 1)Keeping the stock levels at the product table will limit you forever to only one warehouse. It is very simple to plan for more than one warehouses but will be very difficult to do it after. 2)Use only one table for journals. You can separate sale entries from …

Using the given schema, the query is: [code] select * from tblRooms r where not exists (select '0' from tblBookings b, tblLINLK_Bookings t where t.BookingID = b.BookingID and t.RoomID = r.RoomID and (BookingStartDate <= :date_to or BookingEndDate >= :date_from ) [/code] I found the schema correct if: 1)When reservation applies …

What you mean by saying hotel management? My guess is a simple room availability management with a fixed pricing. No complex pricing (if you stay 1 night 100$, 4 nights 90$/night etc), no seasonal offers, no loyalty discounts, no room reservation reselling (like TUI), no expenses, costing etc. Please give …

Technically there is no problem on using date in the key. If you expect the table to store million of rows, it is better to use only the id as a primary key. Remember that the primary key creates a unique index with the same fields as the key. Updates …

I am not sure that I understood the problem and the schema. A suggestion is to separate completely organization and job mapping. A table is needed for organization schema that is a self join like this: Organization *org_id org_name org_parentid. This whay each organization level/position belongs to one and only …

Some "things can go wrong" notes, especialy in economic crisis time. 1)A booking can be canceled and the can be booked again by another (or the same) customer at a later time. So it is advised to modify the relationship between car and booking from 1-1 to 1-many and add …

'Izraboteni proekti' it is not a a valid table name. you should put an underscore (Izraboteni_proekti).

You may also need the following tables: ad_size:id, name, page_factor (whole page(1), 1/2 of the page(0.5), etc) ad_kind:id, name (single color, 2 colors, full colors, etc, leaflet) ad_page:id, page (front_page, left page, right page, last paget, cover page, etc) In the ad table add the fields: ad_sizeid, ad_kindid, id_pageid (add …

Yes it is correct if you are 100% there will be no exceptions. In the most cases the group pricing applies to almost 100% of the products. BUT the rest near-zero% will blow out your design. What can you do? I think is very simple. Create another table called price_exceptions …

In the following schema: *=Primary key value "0" on "." or whatever you like, but the same everywhere, will be used as "No value" This is because primary key columns are required. The schema: category *category_code category_name product *product_code product_name product_category product_or_option (Options are stored in product table in order …